From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Asmedia USB 1343 crashes
Date: Tue, 02 May 2017 20:14:47 -0600 [thread overview]
Message-ID: <1836649.UZ4SekKbO4@natasha> (raw)
In-Reply-To: <3161884.j9lWOCqbeI@natasha>
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
next prev parent reply other threads:[~2017-05-03 2:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 13:40 Asmedia USB 1343 crashes Thomas Fjellstrom
2017-05-01 14:54 ` Alan Stern
2017-05-01 16:20 ` Thomas Fjellstrom
2017-05-01 17:57 ` Alan Stern
2017-05-01 18:08 ` Thomas Fjellstrom
2017-05-03 2:04 ` Thomas Fjellstrom
2017-05-03 2:14 ` Thomas Fjellstrom [this message]
2017-05-03 17:54 ` Alan Stern
2017-05-03 19:20 ` Thomas Fjellstrom
2017-05-04 15:02 ` Mathias Nyman
2017-05-04 15:17 ` Thomas Fjellstrom
2017-05-02 15:43 ` David Laight
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1836649.UZ4SekKbO4@natasha \
--to=thomas@fjellstrom.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.