I tried to use these 3 patches, but they have to be applied to the -ac3 patch. Are they included in the -ac4 patch ?
So... I'll download the -ac3 patch ASAP to test them, in case they're not included in the -ac4.
For now, I retried -ac4 patch only, on a 2.4.12-pre4 kernel. Now, I have theses symptoms (hope it could help you to see what happens until I could test your three patches) :
1) When booting, with hotplug, I've got this neverending error (same as before, but no hangs) :
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=3 (error=-110)
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=4 (error=-110)
[...]
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=60 (error=-110)
hub.c: new USB device 00:10.3-2, assigned address 61
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=62 (error=-110)
hub.c: new USB device 00:10.3-2, assigned address 63
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=63 (error=-110)
hub.c: new USB device 00:10.3-2, assigned
[...]
2) When stopping hotplug and modprobing ehci-hcd :
# modprobe ehci-hcd
ehci-hcd 00:10.3: VIA Technologies, Inc. USB 2.0
ehci-hcd 00:10.3: irq 19, pci mem f8f6e000
usb.c: new USB bus registered, assigned bus number 4
ehci-hcd 00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Jan-22
usb.c: USB disconnect on device 00:10.0-1 address 2
usb.c: USB disconnect on device 00:10.0-1.1 address 4
hub.c: USB hub found
hub.c: 6 ports detected
usb.c: USB disconnect on device 00:10.0-1.2 address 5
usb.c: USB disconnect on device 00:10.0-2 address 3
And FYI :
# lspci |grep VIA
00:00.0 Host bridge: VIA Technologies, Inc. VT8375 [KM266] Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
00:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233 AC97 Audio Controller (rev 50)
Cheers,
Patrice.
David Brownell wrote:
Could you please tell me if there's a solution or if i could do more tests to let someone make a new patch ? :)
Try the patches in these posts on the "VIA EHCI" thread:
- usb-storage patch from Alan Stern
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=104528462604039&w=2
- QH state machine patch (ehci24-0201)
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=104412640709539&w=2
- Avoid QH re-activation paths (ehci-0216)
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=104544247610918&w=2
To apply that last one to 2.4 you'll likely want to "cd drivers/usb/hcd"
and use "patch -p4". The first two are already in Greg's BK tree, and I'd
not be surprised if some of them were in an "ac" kernel.
Let me know if that helps.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
