Bug 55293
Summary: | (IDE)total lockup during high disk activity | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Shane Zatezalo <shane> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:39:13 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
Shane Zatezalo
2001-10-29 12:49:42 UTC
+Oct 29 07:14:50 a2z kernel: hda: dma_intr: status=0x51 { DriveReady +SeekComplete Error } ehmmmm that usually tells you your disk is dying, or that you have a bad IDE cable........... You could try booting with "ide=nodma" as that reduces the speed so the cable doesn't get used as much.. Please realize that /dev/hda is the system disk on this box. The files being copied to the box with this bug report were on other drives, either off the SIIG udma or the Promise cards. I *believe* I didn't see these dma errors on /dev/hda with earlier rh7.0/7.1 w/ updated (2.4.>=10) kernels. But, to be honest, I could have had dma off for /dev/hda then too. The odd thing is that when the files were copying, the system would just stop. No errors in /var/log/messsages, none in smb's logs, nothing on console. Just a total lockup every time. If it helps, the motherboard is a KT7, with 256MB PC133. No hardware was changed between running 7.1 and then the 7.2 install, and no lockups with 7.1. Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |