From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754990AbdECCOy (ORCPT ); Tue, 2 May 2017 22:14:54 -0400 Received: from mail.tomasu.net ([192.241.222.217]:47280 "EHLO mail.tomasu.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752098AbdECCOu (ORCPT ); Tue, 2 May 2017 22:14:50 -0400 From: Thomas Fjellstrom To: Alan Stern Cc: linux-usb@vger.kernel.org, LKML Subject: Re: Asmedia USB 1343 crashes Date: Tue, 02 May 2017 20:14:47 -0600 Message-ID: <1836649.UZ4SekKbO4@natasha> User-Agent: KMail/5.2.3 (Linux/4.11.0-rc7; KDE/5.28.0; x86_64; ; ) In-Reply-To: <3161884.j9lWOCqbeI@natasha> References: <1695369.IdsbSCFftn@natasha> <3161884.j9lWOCqbeI@natasha> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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