Mar 17 00:45:00 goliath kernel: hda: unexpected_intr: status=0xd0 { Busy }
Mar 17 00:45:10 goliath kernel: hdb: irq timeout: status=0x50 { DriveReady SeekComplete }
Mar 17 00:45:40 goliath last message repeated 3 times
Mar 17 00:45:40 goliath kernel: ide0: reset: success
and after a few hours messages like this starts to appear:
Mar 17 05:53:52 goliath kernel: EXT2-fs error (device 03:41): ext2_add_entry: bad entry in directory #118785: rec_len % 4 != 0 - offset=12288, inode=478933, rec_len=20182, name_len=7
Mar 17 05:53:52 goliath kernel: EXT2-fs error (device 03:41): ext2_find_entry: bad entry in directory #118785: rec_len % 4 != 0 - offset=12288, inode=478933, rec_len=20182, name_len=7
Mar 17 05:53:52 goliath last message repeated 23 times
<and lots more>
You can find the config file at
http://gondor.apana.org.au/~herbert/goliath/goliath.conf
Here are some info from /proc:
from /proc/pci:
Bus 0, device 7, function 1:
IDE interface: Intel 82371SB Natoma/Triton II PIIX3 (rev 0).
Medium devsel. Fast back-to-back capable. Master Capable. Latency=32.
I/O at 0xf000.
and upon booting:
Jan 20 22:26:53 goliath kernel: hda: ST5850A, 815MB w/256kB Cache, CHS=1656/16/63
Jan 20 22:26:53 goliath kernel: hdb: ST5850A, 815MB w/256kB Cache, CHS=1656/16/63
Jan 20 22:26:53 goliath kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Jan 20 22:26:53 goliath kernel: Partition check:
Jan 20 22:26:53 goliath kernel: hda: hda1 hda2 hda3 hda4
Jan 20 22:26:53 goliath kernel: hdb: hdb1
My question is, is this a sure sign of a hardware problem or could this be a
bug in the ide drivers? And if it's a hardware problem, is it more likely to be
the disk controller (which is on-board) or the disk? Thanks.
--
Debian GNU/Linux 1.3 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu