Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1634699

Re: Asmedia USB 1343 crashes

From Thomas Fjellstrom <thomas@fjellstrom.ca>
Newsgroups linux.kernel
Subject Re: Asmedia USB 1343 crashes
Date 2017-05-03 04:20 +0200
Message-ID <tCS3v-6G2-1@gated-at.bofh.it> (permalink)
References <tCnM6-3J1-9@gated-at.bofh.it> <tCnVL-417-11@gated-at.bofh.it> <tCRTP-6vM-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tuesday, May 2, 2017 8:04:28 PM MDT Thomas Fjellstrom wrote:
> On Monday, May 1, 2017 12:08:55 PM MDT Thomas Fjellstrom wrote:
> > On Monday, May 1, 2017 1:57:53 PM MDT Alan Stern wrote:
> > > On Mon, 1 May 2017, Thomas Fjellstrom wrote:
> > > > On Monday, May 1, 2017 10:54:12 AM MDT Alan Stern wrote:
> > > > > On Mon, 1 May 2017, Thomas Fjellstrom wrote:
> > > > > > I've got a 970 Pro gaming aura motherboard with an Asmedia 1343 Usb
> > 
> [snip]
> > 
> > > [lots of resets and warnings cut out]
> > > 
> > > Well, this answers one question: The program not claiming interface 0
> > > is ThreadWeaver::T, whatever that is.  This isn't really an error, but
> > > it is sloppy programming.  You could report it to the maintainers of
> > > that program.
> > > 
> > > The log shows a more or less constant series of warnings and resets as
> > > long as the Android device is plugged in.  This would explain any
> > > unresponsiveness, although it doesn't explain eventual crashes.
> > > 
> > > If you know what that ThreadWeaver program is, and if you don't need
> > > it, you could try disabling or removing it to see if the situation
> > > improves.
> > 
> > I'm not sure what program that comes from either, I'll look it up.
> > 
> > Something to note is that things work fine if suspend is disabled or using
> > the regular usb 2 ports on my motherboard instead of the usb 3 ports.
> > 
> > I also saw different error messages, much more severe ones that caused the
> > xhci host to lock up completely and it didn't seem to need me to plug phones
> > in to cause it. I'll follow up after i get it to happen again.
> 
> I just had a brief lockup, desktop stopped responding, other usb devices not 
> on the usb3 controller. Two android devices were in the process of restarting.
> 
> It doesn't seem to matter what android devices it is.
> 
[snip log]

The usb 3.1 controller seems to be inaccessible. 
It'll probably need a reboot to get working again.

>  
> > > Alan Stern
> 
> 
> 


-- 
Thomas Fjellstrom
thomas@fjellstrom.ca

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Asmedia USB 1343 crashes Alan Stern <stern@rowland.harvard.edu> - 2017-05-01 20:00 +0200
  Re: Asmedia USB 1343 crashes Thomas Fjellstrom <thomas@fjellstrom.ca> - 2017-05-01 20:10 +0200
    Re: Asmedia USB 1343 crashes Thomas Fjellstrom <thomas@fjellstrom.ca> - 2017-05-03 04:10 +0200
      Re: Asmedia USB 1343 crashes Thomas Fjellstrom <thomas@fjellstrom.ca> - 2017-05-03 04:20 +0200
      Re: Asmedia USB 1343 crashes Alan Stern <stern@rowland.harvard.edu> - 2017-05-03 20:00 +0200
        Re: Asmedia USB 1343 crashes Thomas Fjellstrom <thomas@fjellstrom.ca> - 2017-05-03 21:30 +0200
          Re: Asmedia USB 1343 crashes Mathias Nyman <mathias.nyman@linux.intel.com> - 2017-05-04 17:10 +0200
            Re: Asmedia USB 1343 crashes Thomas Fjellstrom <thomas@fjellstrom.ca> - 2017-05-04 17:20 +0200

csiph-web