Hardware, IDE or ext3 problem?

Hardware, IDE or ext3 problem?

[ULISSES FURQUIM FREIRE DA SILVA]

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

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.

Re: Hardware, IDE or ext3 problem?

[ULISSES FURQUIM FREIRE DA SILVA]

> What's your exact chipset ?

00:00.0 Host bridge: Silicon Integrated Systems [SiS] 620 Host (rev 03)
00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)

> 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 ?

 # hdparm -i /dev/hda

/dev/hda:

 Model=QUANTUM FIREBALLlct15 20, FwRev=A01.0F00, SerialNo=313061620944
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=32256, SectSize=21298, ECCbytes=4
 BuffType=DualPortCache, BuffSize=418kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39876480
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4 
 DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 
 AdvancedPM=no WriteCache=enabled
 Drive Supports : ATA/ATAPI-5 T13 1321D revision 1 : ATA-1 ATA-2 ATA-3
ATA-4 ATA-5 

	I noticed that I have to enable DMA for my CD-ROM(/dev/hdb), cause
it's disabled on boot.

-- Ulisses

Re: Hardware, IDE or ext3 problem?

[Lionel Bouton]

On Sun, May 19, 2002 at 04:03:25PM -0300, ULISSES FURQUIM FREIRE DA SILVA wrote:
> 
> > What's your exact chipset ?
> 
> 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 620 Host (rev 03)

You'll be the first that would report a SiS620 specific problem, so it's
very unlikely to be a driver problem.
 
If you didn't have CRC errors with previous distributions and they weren't
configured for UDMA your hardware is simply not capable of UDMA (bad cable
or bad drive). That's not a big problem as the kernel works around.
If you had reliable UDMA before and not now, e-mail me the details of your
last known working kernel/kernel config.

> 00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
> 
> > 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 ?
> 
>  # hdparm -i /dev/hda
> 
> /dev/hda:
> 
>  Model=QUANTUM FIREBALLlct15 20, FwRev=A01.0F00, SerialNo=313061620944
>  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
>  RawCHS=16383/16/63, TrkSize=32256, SectSize=21298, ECCbytes=4
>  BuffType=DualPortCache, BuffSize=418kB, MaxMultSect=16, MultSect=16
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39876480
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes: pio0 pio1 pio2 pio3 pio4 
>  DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 
>  AdvancedPM=no WriteCache=enabled
>  Drive Supports : ATA/ATAPI-5 T13 1321D revision 1 : ATA-1 ATA-2 ATA-3
> ATA-4 ATA-5 

I was not expecting this. Isn't `hdparm -i` supposed to check the current dma
mode with an asterisk? It evens checks the last used dma mode (at least
here) when dma is turned off. Guess I shouldn't have `rm -rf`ed the hdparm
source...

LB.

Re: Hardware, IDE or ext3 problem?

[ULISSES FURQUIM FREIRE DA SILVA]

> If you had reliable UDMA before and not now, e-mail me the details of your
> last known working kernel/kernel config.

	Hmm.. my last kernel was a 2.2.17 and I remember of seeing
'*udma2' in the output of `hdparm -i`.. but I don't have the kernel config
file. :-( Does this mean I had UDMA??

> I was not expecting this. Isn't `hdparm -i` supposed to check the current dma
> mode with an asterisk? It evens checks the last used dma mode (at least
> here) when dma is turned off. Guess I shouldn't have `rm -rf`ed the hdparm
> source...

	I thought the current dma mode was checked with an asterisk too..
	`hdparm -i /dev/hdb` output shows:
	
	[...]
	DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2
	AdvancedPM=no

	I'm confused.. Should I change my cables? Is there any risk to use
my drive?

-- Ulisses

Re: Hardware, IDE or ext3 problem?

[Andre Hedrick]

Hi Ulisses,

I guess I need to put in a special monster printk to explain the error
events.  You drive, hardware, and data are secure because of a feature I
created, but chose not to patent (nice guy erm sucker et al.).  However
you do have issues that cause the driver to invoke the transfer rate
reduction feature set.  You can simply try put the drive back in the
faster mode and if it likes it fine, otherwise it will down grade again to
stablize throughput.

The choice is to have it continue with multiple retries w/ the higher
transfer rate, or reduce the io rate but have success on a consistant
bases.

Cheers,


Andre Hedrick
LAD Storage Consulting Group

On Sat, 18 May 2002, 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
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>