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 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?
bus pci, device 0000:00:08.2 (driver 2004-May-10) EHCI 0.95, hcd state 1 structural params 0x00002204 capability params 0x00000002 status 0008 FLR command 010009 (park)=0 ithresh=1 period=256 RUN intrenable 37 IAA FATAL PCD ERR INT uframe 1eef port 1 status 001010 POWER sig=se0 OC port 2 status 001010 POWER sig=se0 OC port 3 status 001010 POWER sig=se0 OC port 4 status 001010 POWER sig=se0 OC irq normal 0 err 0 reclaim 0 (lost 0) complete 0 unlink 0
and after a pluging (without uhci for fallback) I get:
bus pci, device 0000:00:08.2 (driver 2004-May-10) EHCI 0.95, hcd state 0 structural params 0x00002204 capability params 0x00000002 status 1000 Halt command 080000 (park)=0 ithresh=8 period=1024 HALT intrenable 00 uframe 0000 port 1 status 003030 POWER OWNER sig=se0 OCC OC port 2 status 003030 POWER OWNER sig=se0 OCC OC port 3 status 003030 POWER OWNER sig=se0 OCC OC port 4 status 003430 POWER OWNER sig=k OCC OC irq normal 0 err 0 reclaim 0 (lost 0) complete 0 unlink 0
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:
Should I try removing the changes in ehci-hcd.c that is marked "turn off port power on all root hub ports" then? Or maybe it the writel(0,&ehci->regs->inter_enable) call after the ehci_reset() there?
-Thomas
-------------------------------------------------------
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