Re: probable PIIX4 problem

Clem Taylor (ctaylor@SRTC.COM)
Fri, 20 Aug 1999 02:45:42 -0400

saliege2@cict.fr wrote:
> When trying hdparm -t /dev/hda on a newly compiled 2.3.14 I'm getting this
> messages logged and hdparm fails :
>
> Aug 20 00:10:31 tom kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> Aug 20 00:10:31 tom kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> Aug 20 00:11:43 tom kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Aug 20 00:11:43 tom kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=6136, sector=6016
> Aug 20 00:11:43 tom kernel: end_request: I/O error, dev 03:00 (hda), sector 6016
>
> fsck doesn't find error on the drive.
> using dual PII 350 with 440BX chipset and a quantum fireball 3.2Go
>
> I'm also getting errors of the same kind when mounting my ide zip drive, but
> the mount (and the drive works)

I see a similar error on my brand new IDE disk (IBM-DJNA-371800) running
2.2.11 on a Tyan Thunderbolt, which also has the PIIX4 chipset.

Linux version 2.2.11 (root@squeamish) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #2 SMP Fri Aug 6 08:10:24 EDT 1999
Aug 18 02:03:03 squeamish kernel: hda: write_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 18 02:03:03 squeamish kernel: hda: write_intr: error=0x10 { SectorIdNotFound }, LBAsect=14634227, sector=1493221
Aug 18 03:39:13 squeamish kernel: hda: write_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 18 03:39:13 squeamish kernel: hda: write_intr: error=0x10 { SectorIdNotFound }, LBAsect=14196987, sector=1055867
Aug 18 03:40:20 squeamish kernel: hda: write_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 18 03:40:20 squeamish kernel: hda: write_intr: error=0x10 { SectorIdNotFoun d }, LBAsect=14210045, sector=1068917

Most of the time it happens a few times a day, however a few times it
wedged the machine. Before it died klogd consumed 100% cpu. Maybe
generating the message causes klogd to write to the disk which causes the
error to repeat.

I did a fsck blockcheck and it didn't find and problems with the disk.

Any ideas?
Clem

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/