linux-kernel - Re: Asmedia USB 1343 crashes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1705011052290.1893-100000@iolanthe.rowland.org>
Date:   Mon, 1 May 2017 10:54:12 -0400 (EDT)
From:   Alan Stern <stern@...land.harvard.edu>
To:     Thomas Fjellstrom <thomas@...llstrom.ca>
cc:     linux-usb@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Asmedia USB 1343 crashes

On Mon, 1 May 2017, Thomas Fjellstrom wrote:

> I've got a 970 Pro gaming aura motherboard with an Asmedia 1343 Usb 3.1 
> controller. It's been consistently throwing errors and eventually crashing and 
> becomming unresponsive.

Maybe if you posted a kernel log showing those errors, people would 
have a better idea of what's causing your problems.

> Even just plugging in one device to the rear port will eventually cause the 
> controller to die. Usually only takes a few hours for it to completely die.
> 
> 
> One of the errors that shows up consistently is:
> 
> usbfs: process did not claim interface 0 before use

This warning message is not related to the Asmedia controller.  It 
refers to some program running on the computer, and the same message 
would appear no matter what sort of controller was being used.

Alan Stern

> Later on, devices start to throw errors and eventually everything goes away.
> 
> A little while ago, I disabled usb autosuspend and things seem to be behaving.
> 
> I'm currently running 4.11-rc7 but the issue appeared on several earlier 
> kernels as well.