IDE errors with 2.0.11

Kevin M Bealer (kmb203@psu.edu)
Wed, 7 Aug 1996 00:00:36 -0400 (EDT)

These critters appeared on all the open VC's (or is it VT's?)
today. This is with 2.0.11 and a Maxtor 520 MB (about) hard
drive, a few years old, IDE.

hda: write_intr: status=0x51 { DriveReady SeekComplete Error }
hda: write_intr: error=0x04 { DriveStatusError }

I have had this happen with recent kernels.. (I may have
mentioned it before on here). These are very intermittent, and
at least the recent ones haven't shown visible (to e2fsck)
filesystem corruption.

Is this a harmless error? Does it mean corruption? Is my drive
creeping towards the ancient IDE burial ground?

How do I tell if my MB has a CMD640 on it?

Relevant .config flags:

# CONFIG_PCI is not set

CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDE_PCMCIA is not set
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_CMD640_ENHANCED=y
# CONFIG_IDE_CHIPSETS is not set

# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_DEV_HD is not set

# CONFIG_SCSI is not set

# CD-ROM drivers (not for SCSI or IDE/ATAPI drives)
#
CONFIG_CD_NO_IDESCSI=y
CONFIG_SBPCD=m

#
# Filesystems
#
(i wont bore you, it's all the dos junk, minix as mods and ext2=y)
(raid and loop as mods but I don't use them right now.)

# Kernel hacking
#
# CONFIG_PROFILE is not set

__kmb203@psu.edu_______________Debian/GNU__1.1___Linux__2.0.11___
To A Quick Young Fox:
Why jog exquisite bulk, fond crazy vamp,
Daft buxom jonquil, zephyr's gawky vice?
Guy fed by work, quiz Jove's xanthic lamp --
Zow! Qualms by deja vu gyp fox-kin thrice.
-- Lazy Dog