mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: list linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.4.18: many IDE errors
Date: Sun, 24 Mar 2002 19:03:16 +1100	[thread overview]
Message-ID: <3C9D8844.8DA9298C@eyal.emu.id.au> (raw)

I have six disks in the machine, each a master on the cable. Two are
on the on-board controller and Four are on two PCI ATA-100 cards.

I am getting disk error (BadCRC) on all disks, intermittently.

I upgraded from RH 2.4.9 (with SGI xfs) to 2.4.18+xfs. Same problem.
I then applied the 2.4.18-rc1 IDE patches with no improvement (well,
the four 160GB disks are now fully visible and not clipped to 28bits
which is a nice surprise).

I checked the memory, replaced the power supply with a hefty 400W,
I even used a recent mobo (Gigabyte GA-6VTXE). No beef, practically
the same rate of errors.

I do not believe all six cables are bad (80w all). This is a UP, and
I did not enalbe local APIC. Should I?

Any ideas where to go from here? On request I have boot messages
(with errors) and lspci output - I prefer not to overload the list.

The setup is two WD 60GB disks (hda/hdc) which host the root fs (ext2)
a working area (md2=RAID0, most of the space) and an xfs log
(md1=RAID1).

hde/g/i/k are Maxtor 160GB, RAID5, xfs (with external log on md0).

I get errors intermittently on all, here is an example after a boot
following the creation of the raid5 (so a sync was running for about
two hours).

hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide1: reset: success
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
md: md1: sync done.
raid5: resync finished.
hdi: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdi: dma_intr: error=0x84 { DriveStatusError BadCRC }
invalidate: busy buffer


--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>

             reply	other threads:[~2002-03-24  8:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-24  8:03 Eyal Lebedinsky [this message]
2002-03-24  8:21 ` Andre Hedrick
2002-03-24 12:27   ` Eyal Lebedinsky
2002-03-24 22:18     ` Vojtech Pavlik
2002-03-25 10:03     ` Andre Hedrick
2002-03-25 10:26       ` Eyal Lebedinsky
2002-03-25 10:32         ` Andre Hedrick
2002-03-25  9:58   ` Eyal Lebedinsky
     [not found] <Pine.LNX.4.30.0203242314350.31118-100000@mustard.heime.net>
2002-03-24 22:24 ` Eyal Lebedinsky
2002-03-25  9:22   ` Vojtech Pavlik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C9D8844.8DA9298C@eyal.emu.id.au \
    --to=eyal@eyal.emu.id.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®