On Mon, 7 Aug 2006, Steve wrote:

> Hello!  I've searched the lists, and have often found this problem 
> reported, but with no solutions (or none that seem to work for me). 
> Hopefully someone can help me out.  :)
> 
> I have a new Maxtor external 300GB usb hard disk. I was able to use it as 
> a high-speed USB2 device with kernel 2.6.16.1, however, when I recently 
> upgraded to 2.6.17.4, ehci-hcd fails to connect to the drive, instead it 
> times out with:
> 
> usb 1-2: khubd timed out on ep0in len=18/64
> usb 1-2: khubd timed out on ep0out len=0/0
> etc. (all the details in the attached text files)
> 
> Again, in /var/log/messages I find there are many repetitions:
> usb 1-2: new high speed USB device using ehci_hcd and address 2
> etc
> 
> (where the address increments about every 12 secs never stopping)
> 
> (It seems the USB hub is given a device no., but never the attached 
> drive.)
> 
> When I reverted to the kernel 2.6.16.1, everything works fine again at 
> high speed.  I tried the 2.6.16.24 kernel, and found that it is also 
> broken.  For now I am remaining with 2.6.16.1.  I'm not able to test 
> every minor kernel revision between 1 and 24, so I'm not sure what 
> changes.  :)  But it does seem there is a problem that enters after 
> 2.6.16.1 (or else a correction that foils my broken hardware?)
> 
> I have attached debugging output from messages/debug from both 2.6.16.1 
> (which works) and 2.6.17.4 (which doesn't).  (PS. Is this the appropriate 
> list?)  I have also attached the output of lsusb from both kernel 
> versions.
> 
> I am using an Averatec 3225H/S laptop, (VIA chipset, which apparently has 
> some irq problems regarding USB? but don't think this is related), and I 
> run slackware-current.  I have tried booting with "acpi=off noapic" and 
> "acpi=noirq", which has had some success with others, but unfortunately 
> not with me (nor which I require for 2.6.16.1 to work properly with usb2).
> 
> Any thoughts?

Judging from your logs, it looks like this might be a problem with the VIA 
interrupt handling in the later kernels.

By the way, you don't need to try _every_ kernel between 2.6.16.1 and 
2.6.16.24 to pinpoint the breakage.  Binary search is a very effective 
technique.

Alan Stern


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to