On Sun, Mar 18, 2001 at 11:00:30AM -0600, Kazushi Marukawa wrote:
> Hi,
> 
> I updated my current kernel from March 8 version to today's
> version.  Newer kernel detects PROMISE Ultra 100 card and
> Max60 (ATA100 support) combination as Ultra-DMA mode 5
> (Ultra/100).  That's great.  However, then, it finds CRC
> errors and doesn't work well after automatic downgrading of
> DMA mode.  Moreover, it downgrade from UDMA5 to 2 directly.
> ;-)
> 
> This combination works fine as UDMA 100 under Win98/Win2k.

Well, windows doesn't tell you about soft errors. 

> It also works fine as Ultra DMA mode 4 (Ultra/66) with a
> kernel before March 8.  Does it works fine on Ultra 100 card
> and other hard disks configuration?

I tested it with a Ultra/100 IBM disk, works fine.

> 
> 
> Messages about devices and errors are below:
> 
> pciide1 at pci0 dev 10 function 0: Promise Ultra100/ATA Bus Master IDE Accelerator (rev. 0x02)
> pciide1: bus-master DMA support present
> pciide1: primary channel configured to native-PCI mode
> pciide1: using irq 12 for native-PCI interrupt
> wd1 at pciide1 channel 0 drive 0: <Maxtor 96147U8>
> wd1: drive supports 16-sector PIO transfers, LBA addressing
> wd1: 58623 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 120060864 sectors
> wd1: 32-bit data port
> wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
> wd1(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA data transfers)
> 
> 
> Kernelized RAIDframe activated
> wd1: transfer error, downgrading to Ultra-DMA mode 2
> wd1(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA data
> transfers)
> wd1d: aborted command, interface CRC error reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying

Hum, CRC errors ... the data got corrupted on the wire.
Check cables.

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
--