Bug 246128
Summary: | [rhts] usb errors on boot up | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Don Zickus <dzickus> |
Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> |
Status: | CLOSED NOTABUG | QA Contact: | Martin Jenner <mjenner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
URL: | http://rhts.lab.boston.redhat.com/cgi-bin/rhts/test_log.cgi?id=208829 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-06 22:57:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Don Zickus
2007-06-28 18:18:20 UTC
I don't think I can do anything here. Sorry, Don. But I'll look at the spec once again and re-check if we're doing something wrong. It appears that EHCI gets initialized when Avocent (on context of a child of udev, running modprobe) continues to initialize. We were lucky and it happened when HID was fetching string descriptors. Then, for some reason, transmission failed. It would be understandable if EHCI tried to take over the port, but the device were low-speed, like a keyboard. The details of EHCI taking over is something that I do not know well, see above. The odd thing is how Avocent is actually a High-Speed device, I know that. Note that it has storage slots. It should have been taken over by EHCI. Maybe the cable is too long or too thin. The right thing to do is to load ehci_hcd first and its component controller drivers later. This way EHCI drives everything that turned out to be capable of High-Speed, and the companion collects what fell out of the bag. But something prevents us from doing that... I don't remember, maybe we ought to ask Bill Nottingham. It's in mkinitrd somewhere, I believe. I appreciate you looking at this Pete. The problem may not be the software, but is there anything you can recommend (besides the mkinitrd thing) that we could try? Perhaps swap out usb cables, change some sort of configuration, upgrade the BIOS? |