On Fri, 15 Mar 2013, Noone Nowhere wrote: > Hello ,here are the logs from the failing EHCI hosts(chipset-SL > Spec/revision@mainboard-system): > > > ICH4-SL66K@FIC VC37 > 00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM > (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01) (prog-if 20 > [EHCI]) > Subsystem: FIRST INTERNATIONAL Computer Inc Device [1509:9016] > ICH5-SL7YC@ASRockP4i65G > 00:1d.7 USB Controller [0c03]: Intel Corporation 82801EB/ER > (ICH5/ICH5R) USB2 EHCI Controller [8086:24dd] (rev 02) (prog-if 20 > [EHCI]) > Subsystem: ASRock Incorporation Device [1849:24d0] > ICH5R-SL724@ASUS P4P800 SE > 00:1d.7 USB Controller [0c03]: Intel Corporation 82801EB/ER > (ICH5/ICH5R) USB2 EHCI Controller [8086:24dd] (rev 02) (prog-if 20 > [EHCI]) > Subsystem: ASUSTeK Computer Inc. P4P800/P5P800 series motherboard [1043:80a6] > ICH7-SL8FX@ASRock P4i945GC > 00:1d.7 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 > EHCI Controller [8086:27cc] (rev 01) (prog-if 20 [EHCI]) > Subsystem: ASRock Incorporation Device [1849:27cc] > 8237S@ASRock P4VM900 > 00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 > [1106:3104] (rev 90) (prog-if 20 [EHCI]) > Subsystem: ASRock Incorporation K7VT6 motherboard [1849:3104] > A50M FCH-A13@COMPAQ CQ57 > This one has 2 EHCI controllers so we attach both(in fact it has 3 but > 1 is disabled). > 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] (prog-if 20 [EHCI]) > Subsystem: Hewlett-Packard Company Device [103c:3577] > 00:16.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI > SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] (prog-if 20 [EHCI]) > Subsystem: Hewlett-Packard Company Device [103c:3577] > This was the only host giving error message at the program: > URB timed out; bug may be present > Wrong URB completed Evidently hardware from a large number of vendors is affected by this bug. You have to wonder if they all got the intellectual property from a common source. > We thought to use a NEC hub on our broken laptop in order to get the > bug fixed by the hub but the results did not make us happy(stupid idea > for stupid hardware). Additionally we have tested the program on two > more different hubs. We haven't tested our 3.0 hub. Do you think there > is any change to fall on a broken hub while running on a good host and > make the error come to surface? Please mention if it has to be run on > hubs. Here are the results: Hubs will not make any difference. There's no reason to use a hub. > , hope you figure out what you need. You can now see the full picture, > as said on the first message the subject must change because it is not > intel specific. Intel though was consistent all their initial > southbridges were broken while other vendors broke their good EHCI > controller. Good luck with fixing, we can test any patch prior > merging. Unfortunately one SiS 478 board died after POST and we > couldn't test it so R.I.P until service! Thank you very much for all the testing. We may find that the workaround isn't needed on certain chipsets, but we can't know which ones without testing them. The workaround patch is here: http://marc.info/?l=linux-usb&m=136215301302639&w=2 It will apply to a 3.8 kernel. After applying that patch, you should find that the EHCI bug doesn't show up. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
