Description of problem: When my system boots i see the nash message, the system appears to freeze but after several minutes it continues. Booting with quiet mode off I found the problem was in ahci. This section is where the system freezes and if it wasnt for the qc timeout (see below) I dont think it would return. I only have one sata drive connected to 1 of 4 ports, it is the last one probed, it is a wd360 raptor and is connected to SATA1. Also the IDE active LED turns on at this time and never turns off. After the long timeouts the system boots normally and I have never had another problem. Both the PATA and the SATA drive perform without any problems. I do wish the HDD LED would turn off and the system would boot more efficiently. scsi0 : ahci ata2: SATA link down (SStatus 0) ata2: qc timeout (cmd 0xec) ata2: dev 0 failed to IDENTIFY (I/O error) scsi1 : ahci ata3: SATA link down (SStatus 0) ata3: qc timeout (cmd 0xec) ata3: dev 0 failed to IDENTIFY (I/O error) scsi2 : ahci ata4: SATA link down (SStatus 0) ata4: qc timeout (cmd 0xec) ata4: dev 0 failed to IDENTIFY (I/O error) scsi3 : ahci Vendor: ATA Model: WDC WD360GD-00FN Rev: 35.0 Type: Direct-Access ANSI SCSI revision: 05 Version-Release number of selected component (if applicable): How reproducible: The problem occurs everytime I boot. Steps to Reproduce: 1. cold boot 2. warm boot 3. Actual results: Expected results: Additional info: I think the mbr is on the PATA drive. If I disable the SATA ports in the BIOS the system boots normally. Even when no SATA drives are connected the long timeouts occur. ASUS A8R-MVP, Athlon64 3800+, 1GB DDR400, ATI X1600XT Graphics
Reassigning to correct owner, kernel-maint.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) 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 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. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
(In reply to comment #2) The 2.6.18-1.2200.fc5 did completely solve the problem. no delay in loading ahci and hard drive LED behaves normally. I had been running with sata disabled and only using the pata drive. After the kernel update I enabled the sata drive and it functioned with no problems whatsoever. I think it must have been a problem in ahci with my ULI1575 south bridge. Now that I have everyhing working I thought I would try fedora core 6 :(. What you fixed in this kernel is broke again except it makes the system unstable (reboot randomly), disabling sata fixed the stability problem. many bugs later I gave up and reinstalled FC5, it is a rock solid system on my machine now. Should I submit a new bug for FC6? > A new kernel update has been released (Version: 2.6.18-1.2200.fc5) > 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 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. > In the last few updates, some users upgrading from FC4->FC5 > have reported that installing a kernel update has left their > systems unbootable. If you have been affected by this problem > please check you only have one version of device-mapper & lvm2 > installed. See bug 207474 for further details. > If this bug is a problem preventing you from installing the > release this version is filed against, please see FCMETA_INSTALL. > If this bug has been fixed, but you are now experiencing a different > problem, please file a separate bug for the new problem. > Thank you.
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.