Bug 129665
Summary: | usb system no longer recognizes flash drive | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kevin Taylor <ktaylor> | ||||||||
Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> | ||||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 2 | CC: | byte, moneta.mace, riel, wtogami | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | i686 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2005-04-16 05:41:09 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: | |||||||||||
Attachments: |
|
Description
Kevin Taylor
2004-08-11 17:24:22 UTC
Anyone out there? Looks that the EHCI is busted on the motherboard for some reason. Maybe it's not connected at all and not joined with a companion controller. Just remove ehci_hcd from /etc/modprobe.conf for now. I disagree. I boot the old kernel (2.6.6-1.435.2.3) and ehci_hcd works fine, new kernel 2.6.7-1.494.2.2 does not. Doesn't seem like a hardware issue. Comment #3 directly contradicts the initial report: "2.6.6-1.435.2.3 kernel recognized usb 2 devices through the uhci_hcd system []" What do I believe? Please boot the system using 2.6.6-1.435.2.3 and capture dmesg (with dmesg > /tmp/d1.dump), do the same on the 2.6.7-1.494.2.2, attach results to the bug. Please do not drop dmesg outputs into comments box! oops. I made a typo, that would explain the confusion. It was supposed to say ehci_hcd. Created attachment 102827 [details]
2.6.6 dmesg output
The ehci_hcd section here shows proper initialization identifying the bus as
USB 2.0
Created attachment 102828 [details]
2.6.7 dmesg output
The 2.6.7 kernel output shows that ehci_hcd produced an error and fails to
uhci_hcd which doesn't work.
@@ -87,22 +87,40 @@ Linux Plug and Play Support v0.97 (c) Adam Belay usbcore: registered new driver usbfs usbcore: registered new driver hub +PCI: Using ACPI for IRQ routing ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 +ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 11 (level, low) -> IRQ 11 +ACPI: PCI interrupt 0000:00:1d.0[A] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5 +ACPI: PCI interrupt 0000:00:1d.1[B] -> GSI 5 (level, low) -> IRQ 5 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 +ACPI: PCI interrupt 0000:00:1d.2[C] -> GSI 10 (level, low) -> IRQ 10 +ACPI: PCI interrupt 0000:00:1d.3[A] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 9 +ACPI: PCI interrupt 0000:00:1d.7[D] -> GSI 9 (level, low) -> IRQ 9 +ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 10 (level, low) -> IRQ 10 +ACPI: PCI interrupt 0000:00:1f.2[A] -> GSI 10 (level, low) -> IRQ 10 ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 3 -PCI: Using ACPI for IRQ routing +ACPI: PCI interrupt 0000:00:1f.3[B] -> GSI 3 (level, low) -> IRQ 3 +ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 3 (level, low) -> IRQ 3 +ACPI: PCI interrupt 0000:01:01.0[A] -> GSI 10 (level, low) -> IRQ 10 +TC classifier action (bugs to netdev.com cc hadi) vesafb: probe of vesafb0 failed with error -6 apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) ..... @@ -121,6 +139,7 @@ ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH5: IDE controller at PCI slot 0000:00:1f.1 PCI: Enabling device 0000:00:1f.1 (0005 -> 0007) +ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 10 (level, low) -> IRQ 10 ICH5: chipset revision 2 ..... ACPI: Sleep Button (CM) [SLPB] +ACPI: PCI interrupt 0000:00:1d.7[D] -> GSI 9 (level, low) -> IRQ 9 ehci_hcd 0000:00:1d.7: EHCI Host Controller -PCI: Setting latency timer of device 0000:00:1d.7 to 64 -ehci_hcd 0000:00:1d.7: irq 9, pci mem 21bf2c00 -ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 -PCI: cache line size of 128 is not supported by device 0000:00:1d.7 -ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10 -hub 1-0:1.0: USB hub found -hub 1-0:1.0: 8 ports detected +ehci_hcd 0000:00:1d.7: BIOS handoff failed (104, 1010001) +ehci_hcd 0000:00:1d.7: can't reset +ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -95 +ehci_hcd: probe of 0000:00:1d.7 failed with error -95 USB Universal Host Controller Interface driver v2.2 +ACPI: PCI interrupt 0000:00:1d.0[A] -> GSI 11 (level, low) -> IRQ 11 uhci_hcd 0000:00:1d.0: UHCI Host Controller PCI: Setting latency timer of device 0000:00:1d.0 to 64 uhci_hcd 0000:00:1d.0: irq 11, io base 0000c800 -uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2 -hub 2-0:1.0: USB hub found -hub 2-0:1.0: 2 ports detected +uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 +hub 1-0:1.0: USB hub found +hub 1-0:1.0: 2 ports detected +ACPI: PCI interrupt 0000:00:1d.1[B] -> GSI 5 (level, low) -> IRQ 5 uhci_hcd 0000:00:1d.1: UHCI Host Controller PCI: Setting latency timer of device 0000:00:1d.1 to 64 Drats, it's the broken BIOS. I knew it would happen to someone... But I think I can come up with a workaround. Let me look at 2.6.7-1.494.2.2 real quick here. Created attachment 102911 [details]
Candidate #1 - from -mm
I noticed fc2 just released 2.6.8-1.521 I suppose those changes aren't in there? They're not. We may be moving to 2.6.8-1.521 soon just because it fixes some other problems we were seeing with regards to networking. Will those changes still apply or will they make it in the next kernel you ship? Regarding upstream, the fix is not in 2.6.8.1, but it is in 2.6.9-rc1. If Arjan bases next update on 2.6.9-rc1 or later, the fix will make it. Kevin, is a Rawhide kernel acceptable for you? I'm not in a position to push for new FC2 rebuilds. Unfortunately not. We want to avoid custom kernels when possible. Kevin, how about trying the current rawhide kernel to see if the problem gets fixed. If it is, just report back saying "its been fixed". You'll be rewarded with a nice new kernel in due time (thats from updates) Pete: davej is apparently working on an FC2 update, w/2.6.9 goodness I can give it a whack. Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you. |