On Wed, 6 Jul 2011, Ed Endejan wrote: > Here is a look at the registers in two cases as specified below for comparison: > > #### After failure (device was disconnected, but still shows up in lsusb) ##### > # lsusb > Bus 001 Device 001: ID 1d6b:0002 > Bus 002 Device 001: ID 1d6b:0002 > Bus 002 Device 002: ID 0424:2513 > Bus 002 Device 007: ID 05ac:1266 > # mount -t debugfs debugfs /sys/kernel/debug/ > # cd /sys/kernel/debug/usb/ehci/ehci-omap.0 > # cat registers > bus platform, device ehci-omap.0 > OMAP-EHCI Host Controller > EHCI 1.00, hcd state 1 > structural params 0x00001313 > capability params 0x00000016 > status 4008 Periodic FLR > command 010019 (park)=0 ithresh=1 Periodic period=256 RUN > intrenable 37 IAA FATAL PCD ERR INT > uframe 2d2a > port 1 status 001005 POWER sig=se0 PE CONNECT > port 2 status 001000 POWER sig=se0 > port 3 status 001000 POWER sig=se0 > irq normal 222 err 70 reclaim 180 (lost 0) > complete 290 unlink 26 > > #### After subsequent reboot, but prior to any device connect/disconnect ##### > # lsusb > Bus 001 Device 001: ID 1d6b:0002 > Bus 002 Device 001: ID 1d6b:0002 > Bus 002 Device 002: ID 0424:2513 > # mount -t debugfs debugfs /sys/kernel/debug/ > # cd /sys/kernel/debug/usb/ehci/ehci-omap.0 > # cat registers > bus platform, device ehci-omap.0 > OMAP-EHCI Host Controller > EHCI 1.00, hcd state 1 > structural params 0x00001313 > capability params 0x00000016 > status 4008 Periodic FLR > command 010019 (park)=0 ithresh=1 Periodic period=256 RUN > intrenable 37 IAA FATAL PCD ERR INT > uframe 2daf > port 1 status 001005 POWER sig=se0 PE CONNECT > port 2 status 001000 POWER sig=se0 > port 3 status 001000 POWER sig=se0 > irq normal 17 err 0 reclaim 5 (lost 0) > complete 16 unlink 0 That's not very helpful, unfortunately. The two files are basically the same. Maybe the other files in that directory will be more useful. Let's see what they show after the device is plugged in but before you run the test program, and then again after the test program fails. Another great thing to do, if you can, would be to hook up a bus analyzer to see what's passing between the controller and your special hub. 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
