Bug 160698
| Summary: | Unable to access external USB 2.0 hard drive | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Thomas Cameron <thomas.cameron> | ||||||||||||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | medium | ||||||||||||||||
| Version: | 5 | CC: | davej, jbaron, pfrields, rlocke, wtogami | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | i386 | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | fc5 | Doc Type: | Bug Fix | ||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2006-09-17 04:26:38 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
Thomas Cameron
2005-06-16 18:42:10 UTC
Do any other 2.0 devices work? I'll need full dmesg and /proc/interrupts. Please do not drop them into the comments box, but attach to the bug instead. Created attachment 115588 [details]
dmesg
Created attachment 115589 [details]
interrupts
If you need direct access to the machine I can provide you a login and sudo access, just let me know. Red Hat employees never access anyone's comuters remotely. Too much liability. Can you get an FC3 kernel onto the same box? It can be installed, perhaps with small amount of force. I'd like to see the same dmesg taken on it, so it shows interrupt routing. Created attachment 115757 [details]
output of dmesg
Created attachment 115758 [details]
/proc/interrupts
The non-working kernel is running with: Kernel command line: ro root=LABEL=/ vga=791 noacpi Small wonder that disabled ACPI results in this: ACPI: PCI Interrupt 0000:00:1d.7[D]: no GSI - using IRQ 11 That BIOS probably hasn't got a decent PIR$ table at all. Why is this box running with ACPI disabled? Please try without "noacpi". Sorry, I should have made clear. The first boot where I saw the error did NOT have noacpi. I tried noacpi based on info I found on a Google search. It did not help. So the behavior is the same with or without noacpi. Do you still want me to try with FC4 again? I will have to re-install, as I put RHEL 4 on here. I need the non-working dmesg with ACPI then. [This comment has been added as a mass update for all FC4 kernel bugs. If you have migrated this bug from an FC3 bug today, ignore this comment.] Please retest your problem with todays 2.6.12-1.1398_FC4 update. If your problem involved being unable to boot, or some hardware not being detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE* installing any kernel updates. If in doubt, you can recreate this file using.. mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak mv /etc/modprobe.conf /etc/modprobe.conf.bak kudzu Thank you. Created attachment 117519 [details]
dmesg output
This is dmesg with a fresh install of FC4. I just installed and ran yum -y
update, so I am now at kernel 2.6.12-1.1398_FC4.
Created attachment 117520 [details]
/proc/interrupts
This is /proc/interrupts with a fresh install of FC4. I just installed and ran
yum -y update, so I am now at kernel 2.6.12-1.1398_FC4.
Mass update to all FC4 bugs: An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream kernel (2.6.13.2). As there were ~3500 changes upstream between this and the previous kernel, it's possible your bug has been fixed already. Please retest with this update, and update this bug if necessary. Thanks. 2.6.14-1.1637_FC4 has been released as an update for FC4. Please retest with this update, as a large amount of code has been changed in this release, which may have fixed your problem. Thank you. This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you. I am no longer using FC at all, strictly RHEL. I can't really do any more with this, suggest closing the BZ. [This comment added as part of a mass-update to all open FC4 kernel bugs] FC4 has now transitioned to the Fedora legacy project, which will continue to release security related updates for the kernel. As this bug is not security related, it is unlikely to be fixed in an update for FC4, and has been migrated to FC5. Please retest with Fedora Core 5. Thank you. |