Bug 49614 - dma disk errors hangs hangs install
Summary: dma disk errors hangs hangs install
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-07-21 16:20 UTC by Bill Faust
Modified: 2007-04-18 16:34 UTC (History)
0 users

Clone Of:
Last Closed: 2001-07-23 19:22:46 UTC

Attachments (Terms of Use)

Description Bill Faust 2001-07-21 16:20:49 UTC
Description of Problem:
Installer hangs when installing packages with first error being "hda:
dma_intr: status=0x51" and then "hda: dma_intr: status: 0x84" as first two
errors.  Then a bunch of timout errors waiting on drive to come ready.

How Reproducible:
Every time.

Steps to Reproduce:
1. Boot from floppy "bootnet.img".
2. Perform FTP network install.
3. Will hang on one of the first few packages it installs as described

Actual Results:
I get the error messages and installation program hangs forever.

Expected Results:
A nice clean install with a friendly "Thank you for installing RedHat 7.1!"

Additional Information:

I have five identical machines and the bug appears on all of them, so a
hardware problem is unlikely.  Also, all machines CAN load RedHat 6.2
correctly.  Problem appears in 7.1.

Motherboard: FIC SD-11
CPU: Athlon 600 MHz (Slot A)
Harddrive: Maxtor 8216002 (2 GB, 4465/15/63)
Ethernet Card: Some cheap NE2000 PCI
Video card: varied

Some of the things I have tried:

1. Updated BIOS to version NC611 (the latest)
2. Since the problem appeared to be with DMA, I tried boot options like:
   "linux ide=nodma"
   "linux hda=nodma ide=nodma"
   "linux hda=nodma ide=nodema floppy=nodma"
I thought it strange that it still gave the dma error even though I had
these kernel options specified.
3. Disabling all I could think to in the BIOS.  Unfortunately I could not
find a switch to disable DMA.

This bug report is similar to others I have found regarding DMA errors but
theirs did not seem as severe, as they were still able to install.

Comment 1 Brent Fox 2001-07-23 15:16:11 UTC
Changing component to the kernel.

Comment 2 Arjan van de Ven 2001-07-23 15:24:59 UTC
Any idea what chipset this is ?
And are the IDE disks connected to the chipset directly or
to some raid or otherwise special chip ?

Comment 3 Bill Faust 2001-07-23 19:22:41 UTC
Some more information.

1. I went back and tried RH 6.1 and also encountered disk read/write errors on
one of the two systems I am working through this problem with.  So likelihood
that his is hardware problem and not software bug has gone way up.

2. Chipset is AMD 751 North bridge and VIA 686A ("Super South") for South

3. Had a typo on the drive type.  It is a Maxtor 82160D2.

4. There is a lot of information at
http://www.fic.com.tw/techsupport/faq/faqs01SD11.htm on this motherboard with
lots of comments about UDMA 66 problems with Maxtor drives (which I have).

5. I have five computers equipped with this motherboard and while pretty stable,
they have not been nearly as stable as other computers in our little computing
farm of 18 computers.  So maybe I am now just uncovering a long standing problem
with this motherboard/disk combination.

I am suspecting this really isn't a RedHat 7.1 problem right now with the
inability to load even RH 6.1 via bootnet.img.  Thanks for your prompt
attention.  I will read up on the FIC SD11 hardware issues and see if I can
debug it.  If you want to leave the bug report open then I promise to report
back, but I can understand if you want to close it.

Thanks, Bill Faust

Comment 4 Bill Faust 2001-07-27 15:36:04 UTC
Not a bug.  Definitely hardware problem with this motherboard (FIC SD11) and
UDMA harddrives.  It was an intermittant problem which led me to suspect RedHat
7.1.  On three different computers I replaced existing Maxtor 82160D2 harddrive
with non-UDMA drives: (QUANTUM BIGFOOT1280A on two and WDC AC11200L in the
third), and the problem went away.

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