Bug 54742 - IDE driver failure
IDE driver failure
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.1
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-10-17 13:21 EDT by Tyler Dunlap
Modified: 2007-04-18 12:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-10-17 13:23:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tyler Dunlap 2001-10-17 13:21:40 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (WinNT; U)

Description of problem:
RedHat 7.1 install to the IDE drive appeared to be successful.  Following 
the install the system was rebooted, kernel startup errors are 
displayed and the system hangs.  The last messages on the console are:

Freeing unused kernel memory: 244k freed
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x59 { DriveReady SeekComplete DataRequest Error 
}
hda: irq timeout: error=0x84 {DriveStatusError BadCRC }
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14

Now the system is hung - no response to keyboard input

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Power on system
2.Watch it fail
3.
	

Actual Results:  See console errors reported in description - it's dead

Expected Results:  ----

Additional info
Comment 1 Arjan van de Ven 2001-10-17 13:23:39 EDT
Could you try adding "ide=nodma" to the lilo prompt ?
(eg type ctrl-x to go to the text mode lilo screen, then type "linux ide=nodma")
Comment 2 Tyler Dunlap 2001-10-17 16:14:51 EDT
OK - works great - that was easy 
Thanks

Note You need to log in before you can comment on or make changes to this bug.