Re: Hardware, IDE or ext3 problem?

[Lionel Bouton]

On Sat, May 18, 2002 at 09:08:10PM -0300, ULISSES FURQUIM FREIRE DA SILVA wrote:
> 
> Hi,
> 
> 	I installed Red Hat 7.3 and the 2.4.18-3 kernel shows some IDE
> errors on boot like:
> 
> VFS: Mounted root (ext2 filesystem).
> Journalled Block Device driver loaded
> 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
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> 
> 	I also tried the 2.4.18-4 kernel, but the errors continue. It's
> weird cause this happen only on boot and in spite of it the system runs
> fine.
> 	I have a SiS 5513 chipset with a QUANTUM FIREBALLlct15 20 IDE
> drive.
> 	I'm not sure if I have a true hardware problem or if there is a
> bug in the kernel. Any ideas?
> 	(please CC the answers to me)
> 
> Thanks,
> 
> -- Ulisses
> 

What's your exact chipset ?

`lspci | grep "00:00.0"` should show it.

SiS5513 is the IDE interface device shown on the PCI bus but there are a
hell lot of revisions.

BadCRC can be due to flaky hardware but I guess incorrect timings could be
another source of the problem. The only case of incorrect timings I'm aware
of is for ATA133: SiS645DX (just began working on it).

The IDE code should lower the DMA mode by itself when it sees BadCRC, what's
the output of `hdparm -i /dev/hda` after these errors show up ?

LB.