public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* USB 2.0 (EHCI) keeps crapping out (3.2.29)
@ 2012-12-25  3:02 Logan Rathbone
  2012-12-25  4:10 ` Rob Landley
  0 siblings, 1 reply; 3+ messages in thread
From: Logan Rathbone @ 2012-12-25  3:02 UTC (permalink / raw)
  To: linux-kernel

*** NOTE:  Kindly CC me directly if you reply to list since I'm not an 
LKML subscriber. ***

Running vanilla 3.2.29 (Slackware 14.0).  I also had this issue on 
2.6.37.6 and *possibly* 2.6.33.x, but I don't recall.

Every now and again (could be every few days, could take a couple of 
weeks... depends.) USB 2.0 stops working.  My scanner as well as certain 
mass-storage devices that are USB-2.0 compatible fail to function all of 
a sudden.

With the said mass storage devices, I get lots of errors like this in my 
logs:

hub 1-0:1.0: unable to enumerate USB device on port 3

Devices that have previously been mounted and accessed successfully 
begin giving input/output errors when I try to ls them.

rmmod'ing ehci_hcd and modprobe'ing it again resolves the issue until it 
occurs again.

It *could* be a hardware problem, but it seems odd that unloading & 
reloading the module instantly makes it work perfectly again.

Via USB 1.1/2.0 controller from circa 2002-2003.

If anyone has any ideas, please let me know...

logan@logancomp:~$ /sbin/lspci |grep -i usb
00:10.0 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 
Controller (rev 80)
00:10.1 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 
Controller (rev 80)
00:10.2 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 
Controller (rev 80)
00:10.3 USB controller: VIA Technologies, Inc. USB 2.0 (rev 82)

logan@logancomp:~$ cat /proc/cmdline
auto BOOT_IMAGE=Slackware ro root=802 nohz=off highres=off 
clocksource=jiffies acpi_enforce_resources=lax vt.default_utf8=0

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: USB 2.0 (EHCI) keeps crapping out (3.2.29)
  2012-12-25  3:02 USB 2.0 (EHCI) keeps crapping out (3.2.29) Logan Rathbone
@ 2012-12-25  4:10 ` Rob Landley
  2012-12-25  4:26   ` Logan Rathbone
  0 siblings, 1 reply; 3+ messages in thread
From: Rob Landley @ 2012-12-25  4:10 UTC (permalink / raw)
  To: Logan Rathbone; +Cc: linux-kernel

On 12/24/2012 09:02:11 PM, Logan Rathbone wrote:
> *** NOTE:  Kindly CC me directly if you reply to list since I'm not  
> an LKML subscriber. ***
> 
> Running vanilla 3.2.29 (Slackware 14.0).  I also had this issue on  
> 2.6.37.6 and *possibly* 2.6.33.x, but I don't recall.
> 
> Every now and again (could be every few days, could take a couple of  
> weeks...
> depends.) USB 2.0 stops working.  My scanner as well as certain  
> mass-storage
> devices that are USB-2.0 compatible fail to function all of a sudden.
> 
> With the said mass storage devices, I get lots of errors like this in  
> my logs:
> 
> hub 1-0:1.0: unable to enumerate USB device on port 3

What is the _first_ error that shows up in dmesg when the failure  
occurs?

Rob

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: USB 2.0 (EHCI) keeps crapping out (3.2.29)
  2012-12-25  4:10 ` Rob Landley
@ 2012-12-25  4:26   ` Logan Rathbone
  0 siblings, 0 replies; 3+ messages in thread
From: Logan Rathbone @ 2012-12-25  4:26 UTC (permalink / raw)
  To: Rob Landley; +Cc: linux-kernel



On 12/24/2012 11:10 PM, Rob Landley wrote:
> On 12/24/2012 09:02:11 PM, Logan Rathbone wrote:
>> *** NOTE:  Kindly CC me directly if you reply to list since I'm not an
>> LKML subscriber. ***
>>
>> Running vanilla 3.2.29 (Slackware 14.0).  I also had this issue on
>> 2.6.37.6 and *possibly* 2.6.33.x, but I don't recall.
>>
>> Every now and again (could be every few days, could take a couple of
>> weeks...
>> depends.) USB 2.0 stops working.  My scanner as well as certain
>> mass-storage
>> devices that are USB-2.0 compatible fail to function all of a sudden.
>>
>> With the said mass storage devices, I get lots of errors like this in
>> my logs:
>>
>> hub 1-0:1.0: unable to enumerate USB device on port 3
>
> What is the _first_ error that shows up in dmesg when the failure occurs?

I *think* this is the first error that appears:

usb 1-3: USB disconnect, device number 3
sd 5:0:0:0: Device offlined - not ready after error recovery

That second message is sometimes:

usblp0: removed

But honestly I can't recall if my USB 2.0 printer stopped working at 
that point in time.  The effect of the crap-out is mainly noticeable on 
my mass storage devices since I can't mount them (the device nodes do 
not get created by udev until I rmmod & modprobe ehci_hcd again or reboot).

I also see stuff like this scattered throughout (hard to tell if it's 
one of the first or last errors that pops up though... I think it's the 
last.  It usually pops up after a whole whack of the "unable to 
enumerate" errors:

ehci_hcd 0000:00:10.3: force halt; handshake f8044014 0000c000 00000000 
-> -110

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-12-25  4:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-25  3:02 USB 2.0 (EHCI) keeps crapping out (3.2.29) Logan Rathbone
2012-12-25  4:10 ` Rob Landley
2012-12-25  4:26   ` Logan Rathbone

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox