Bug 192761
| Summary: | SATA Errors prevent installation on MSI K7N2 Nforce 2 with SATA drive | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jeremy Parsons <redhat> |
| Component: | kernel | Assignee: | Dave Jones <davej> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | pfrields, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-11-24 23:19:31 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
Jeremy Parsons
2006-05-22 19:41:18 UTC
The error messages that look most relavent are:
<4>ATA: abnormal status 0xD0 on port 0x977, Scsi parity erro
<3> ata2: command 0x35 timeout stat 0xd0 host)stat 0x21
The good news is that I discovered that by turning the computer on and off
instead of just resetting, and then adding the "nodma" kernel option to the FC5
installation command line ("linux nodma") allowed me to install FC5. After a few
more boots and rescues I had a "nodma" kernel option in my grub menu.lst and I
was able to boot far enough to run "yum update" (on 24th May 2006) which pulled
in the new kernel which supports the specific SATA drivers properly and gives me
65 MB/s on hdparm timed reads. (Kernel 2.4 in DSL without DMA was only able to
get 10 MB/s). It seems to be working so far but reset button still needs to be
followed by on/off to get a complete boot ...
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. This bug has been mass-closed along with all other bugs that have been in NEEDINFO state for several months. Due to the large volume of inactive bugs in bugzilla, this is the only method we have of cleaning out stale bug reports where the reporter has disappeared. If you can reproduce this bug after installing all the current updates, please reopen this bug. If you are not the reporter, you can add a comment requesting it be reopened, and someone will get to it asap. Thank you. |