Bug 34948

Summary: Promise TX2 ATA133 controller doesnt work with 80 wire cable on alpha
Product: Base System Reporter: sten
Component: alphaAssignee: freebsd-alpha (Nobody) <alpha>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description sten 2002-02-15 00:10:02 UTC
I get this error when using an 80 wire udma66/100/133 cable
to connect a maxtor harddrive. I verified this config as working
in a normal pc, in the promise controller screen ( udma6 ).

It looks like the driver doesnt do the correct udma133 initialization on alpha.

     Feb 14 19:07:08 earth /kernel: ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying
Feb 14 19:07:08 earth last message repeated 2 times
Feb 14 19:07:08 earth /kernel: ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) falling back to PIO mode


Switching to an udma33 cable sped things up quite a bit.

Feb 14 23:03:34 earth /kernel: ata2-master: DMA limited to UDMA33, non-ATA66 compliant cable
Feb 14 23:03:34 earth /kernel: ad0: 76345MB <MAXTOR 6L080J4> [155114/16/63] at ata2-master UDMA33

How-To-Repeat: Use a promise udma 133 controller with the supplied cable and a udma133 drive in an alpha.
Comment 1 Andrew Gallatin 2002-02-15 00:14:38 UTC
The driver should be totally machine independent.  I suspect that your
problem might be a hardware problem -- the alpha might be a bit
noisier in terms of EMI than a PC.

Have you verified that it it works with another OS?
(no, I don't know what other OSes are kind enough to tell you about
CRC errors..)

Drew


 > 
 >      Feb 14 19:07:08 earth /kernel: ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying
 > Feb 14 19:07:08 earth last message repeated 2 times
 > Feb 14 19:07:08 earth /kernel: ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) falling back to PIO mode
 > 
 > 
 > Switching to an udma33 cable sped things up quite a bit.
 > 
 > Feb 14 23:03:34 earth /kernel: ata2-master: DMA limited to UDMA33, non-ATA66 compliant cable
 > Feb 14 23:03:34 earth /kernel: ad0: 76345MB <MAXTOR 6L080J4> [155114/16/63] at ata2-master UDMA33
 > 
 > >How-To-Repeat:
 > Use a promise udma 133 controller with the supplied cable and a udma133 drive in an alpha.
 > >Fix:
Comment 2 Søren Schmidt freebsd_committer freebsd_triage 2003-05-05 11:07:10 UTC
State Changed
From-To: open->closed

There was a bug regarding this, but it has been fixed long ago.