Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1633674 > unrolled thread
| Started by | Thomas Fjellstrom <thomas@fjellstrom.ca> |
|---|---|
| First post | 2017-05-01 15:50 +0200 |
| Last post | 2017-05-02 17:50 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.kernel
Asmedia USB 1343 crashes Thomas Fjellstrom <thomas@fjellstrom.ca> - 2017-05-01 15:50 +0200
Re: Asmedia USB 1343 crashes Alan Stern <stern@rowland.harvard.edu> - 2017-05-01 17:00 +0200
RE: Asmedia USB 1343 crashes David Laight <David.Laight@ACULAB.COM> - 2017-05-02 17:50 +0200
| From | Thomas Fjellstrom <thomas@fjellstrom.ca> |
|---|---|
| Date | 2017-05-01 15:50 +0200 |
| Subject | Asmedia USB 1343 crashes |
| Message-ID | <tCjS9-1n9-9@gated-at.bofh.it> |
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. 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 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. -- Thomas Fjellstrom thomas@fjellstrom.ca
[toc] | [next] | [standalone]
| From | Alan Stern <stern@rowland.harvard.edu> |
|---|---|
| Date | 2017-05-01 17:00 +0200 |
| Message-ID | <tCkXT-1YA-9@gated-at.bofh.it> |
| In reply to | #1633674 |
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.
[toc] | [prev] | [next] | [standalone]
| From | David Laight <David.Laight@ACULAB.COM> |
|---|---|
| Date | 2017-05-02 17:50 +0200 |
| Message-ID | <tCIdP-aZ-15@gated-at.bofh.it> |
| In reply to | #1633674 |
From: Thomas Fjellstrom > Sent: 01 May 2017 14:40 > 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. ... I've an earlier Asmedia 1042 controller. It has a bug (which I don't remember seeing a fix for) that it will only process one entry from the command ring each time the doorbell is rung. If more than one command gets queued then it all got very confusing because responses to timed out commands kept being seen. (I no longer have the USB3 ethernet device needed to reproduce this.) The later part might have the same bug. David
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web