On Thu, 17 May 2012, Geoff Levand wrote: > I could just do some quick tests but found that with DEBUG > defined and your change I see these with the port errors > continuing on indefinitely. > > <7>usb 2-2: link qh0-00ff/c00000001bcbf480 start 0 [2/0 us] > <7>usb 1-1: unlink qh256-0001/c00000001d181d00 start 1 [1/0 us] Those two lines look normal. > <3>hub 3-0:1.0: connect-debounce failed, port 1 disabled > <3>hub 3-0:1.0: over-current condition on port 2 > <4>hub 3-0:1.0: config error on port 2 > <3>hub 3-0:1.0: connect-debounce failed, port 2 disabled > <7>ps3-ehci-driver sb_06: GetStatus port:1 status ffffffff 127 ERR POWER OWNER sig=? LPM RESET SUSPEND R > <3>ps3-ehci-driver sb_06: port 1 resume error -19 > <7>ps3-ehci-driver sb_06: GetStatus port:1 status ffffffff 127 ERR POWER OWNER sig=? LPM RESET SUSPEND R > <3>hub 1-0:1.0: over-current condition on port 1 > <3>ps3-ehci-driver sb_06: port 2 resume error -19 > <7>ps3-ehci-driver sb_06: GetStatus port:2 status ffffffff 127 ERR POWER OWNER sig=? LPM RESET SUSPEND R > <3>ps3-ehci-driver sb_06: port 2 resume error -19 > <7>ps3-ehci-driver sb_06: GetStatus port:2 status ffffffff 127 ERR POWER OWNER sig=? LPM RESET SUSPEND R > <3>hub 1-0:1.0: over-current condition on port 2 > <7>ps3-ehci-driver sb_06: GetStatus port:2 status ffffffff 127 ERR POWER OWNER sig=? LPM RESET SUSPEND R > <3>ps3-ehci-driver sb_06: port 2 resume error -19 > <7>ps3-ehci-driver sb_06: GetStatus port:2 status ffffffff 127 ERR POWER OWNER sig=? LPM RESET SUSPEND R > <3>ps3-ehci-driver sb_06: port 2 resume error -19 > ... It looks like the EHCI controllers are not powering on. All those ffffffff values are what you get when you read an unpowered register. It doesn't seem like this could be related to the new patch. I'm puzzled. Let me know when you will have some more time available for testing. Some of the changes in that patch are now in the mainline kernel, which will make things easier. 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
