On Monday 13 December 2004 12:10 pm, Thomas Dodd wrote: > > Did some more digging. Built 2.6.9-1.6_FC with CONFIG_USB_DEBUG=y and > found an older 2.6.5-1.358 kernel. > > With the 2.6.5 kernel, I still see: > ehci_hcd 0000:00:08.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Dec-29 > hub 1-0:1.0: over-current change on port 1 > hub 1-0:1.0: over-current change on port 2 > hub 1-0:1.0: over-current change on port 3 > hub 1-0:1.0: over-current change on port 4 > *****
So basically, there's some power-related issue with this board, which acts innocuous on 2.6.5 kernels. AND with later kernels, the board gets fatal errors ... possibly related. So far that information matches what other folk have reported: problems starting to appear in 2.6.6, on some boards not all. > So with the new kernel, and DEBUG on. Only loading EHCI (no UHCI to fall > back too): > ehci_hcd 0000:00:08.2: init command 010009 (park)=0 ithresh=1 period=256 RUN > ehci_hcd 0000:00:08.2: USB 2.0 enabled, EHCI 0.95, driver 2004-May-10 > ehci_hcd 0000:00:08.2: supports USB remote wakeup > usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1 > usb usb1: default language 0x0409 > usb usb1: Product: EHCI Host Controller > usb usb1: Manufacturer: Linux 2.6.9-1.6_FC2custom ehci_hcd > usb usb1: SerialNumber: 0000:00:08.2 > usb usb1: hotplug > usb usb1: adding 1-0:1.0 (config #1, interface 0) > usb 1-0:1.0: hotplug > hub 1-0:1.0: usb_probe_interface > hub 1-0:1.0: usb_probe_interface - got id > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 4 ports detected > hub 1-0:1.0: standalone hub > hub 1-0:1.0: ganged power switching > hub 1-0:1.0: individual port over-current protection > hub 1-0:1.0: Single TT > hub 1-0:1.0: TT requires at most 8 FS bit times > hub 1-0:1.0: power on to power good time: 20ms > hub 1-0:1.0: local power source is good > hub 1-0:1.0: enabling power on all ports But actually, it _isn't_ enabling power, since this root hub doesn't have power switching. That's just a misleading message. > ehci_hcd 0000:00:08.2: GetStatus port 1 status 001030 POWER sig=se0 OCC OC > hub 1-0:1.0: over-current change on port 1 > hub 1-0:1.0: enabling power on all ports > ehci_hcd 0000:00:08.2: GetStatus port 2 status 001030 POWER sig=se0 OCC OC > hub 1-0:1.0: over-current change on port 2 > hub 1-0:1.0: enabling power on all ports > ehci_hcd 0000:00:08.2: GetStatus port 3 status 001030 POWER sig=se0 OCC OC > hub 1-0:1.0: over-current change on port 3 > hub 1-0:1.0: enabling power on all ports > ehci_hcd 0000:00:08.2: GetStatus port 4 status 001030 POWER sig=se0 OCC OC > hub 1-0:1.0: over-current change on port 4 > hub 1-0:1.0: enabling power on all ports > ******** At that point, what does /sys/class/usb_host/usb1/registers say? The hub driver (khubd) comes into play here too, and that's had more updates than EHCI has since these problems started to appear. I'm wondering what state it put the root hub into ... I've looked over the 2.6.[678] EHCI updates a lot, and haven't noticed anything that'd even kick in on some of the systems that started reporting the nasty failure: > Then plug in a USB2 device: > ehci_hcd 0000:00:08.2: fatal error > ehci_hcd 0000:00:08.2: reset command 01000b (park)=0 ithresh=1 > period=256 Reset RUN > ehci_hcd 0000:00:08.2: HC died; cleaning up > ******** > > This is strange. I really don't know where to go to figure this out. Me either, but it's interesting that there seems to be a quasi-stable state in your setup (before device plugin) that other people have not been reporting. That "registers" dump might be very informative. - Dave ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
