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.
-
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/