atapci VIA 82C596B UDMA66 controller: problem for 5.X ?

Mark Kirkwood markir at paradise.net.nz
Thu Feb 10 21:52:11 PST 2005


Rob,

I am currently running 5.3 Release on a Tyan Trinity 400 (VIA 82C596B 
UDMA66) with 2 x Seagate Barracude IV (UDMA100) and have no stability 
issues. e.g from dmesg:

atapci0: <VIA 82C596B UDMA66 controller> port 
0xe000-0xe00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
ad0: 19092MB <ST320011A/3.10> [38792/16/63] at ata0-master UDMA66
ad1: 19092MB <ST320011A/3.10> [38792/16/63] at ata0-slave UDMA66
acd0: CDRW <CREATIVE CD-RW RW8439E/1R09> at ata1-master PIO4

What does your dmesg show if you dont force ata_dma=0?

Hmmmm - you have an IBM disk in one pc and WDs in the other, hard to 
believe that the disks are the issue. Do both pcs have the same mobo? 
(if so what is it).

Something else - did you upgrade from 4.x or fresh install?


With respect to attempting a fix, you could try

$ atacontrol mode 0 UDMA66 UDMA66

immediately after boot, to see if you can force a sensible transfer mode 
setting.

regards

Mark

Rob wrote:
> Hi,
> 
> I have two PCs, with apparently a somewhat old
> motherboard, since there's a maximum support for
> UDMA66 by the harddisk controller.
> The attached harddisks are newer and allow a
> higher speed of UDMA100.
> 
> This combination of older motherboard and newer
> harddisk causes great problems with 5.X (it never
> did with 4.X). I have irregular crashes of X and
> even crashes at initial bootup. All this is solved
> by using  hw.ata.ata_dma="0", which forces the
> harddisk to use the very low speed of PIO4 :(.
> 
> Both PCs have a VIA 82C596B UDMA66 controller.
> I wonder if that is the problem for 5.X ?
> 
> On these two PCs, the output is of
>    grep -i ata /var/run/dmesg.boot
> is:
> 
> -- PC1 -------------------
> atapci0: <VIA 82C596B UDMA66 controller> port
>   0xe000-0xe00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7
>   at device 7.1 on pci0
> ata0: channel #0 on atapci0
> ata1: channel #1 on atapci0
> ad0: 43979MB <IBM-DTLA-307045/TX6OA50C> [89355/16/63]
>      at ata0-master PIO4
> acd0: CDROM <CRD-8520B/1.00> at ata1-master PIO4
> 
> 
> -- PC2 -------------------
> atapci0: <VIA 82C596B UDMA66 controller> port
>   0xc000-0xc00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7
>   at device 7.1 on pci0
> ata0: channel #0 on atapci0
> ata1: channel #1 on atapci0
> ad0: 76319MB <WDC WD800JB-00CRA1/17.07W17>
>     [155061/16/63] at ata0-master PIO4
> ad1: 16448MB <WDC WD172AA/05.05B05> [33420/16/63] at
>      ata0-slave PIO4
> acd0: CDRW <HL-DT-ST RW/DVD GCC-4320B/1.00> at
>      ata1-master UDMA33
> 
> -------------------------------------------------
> 
> I consider this a serious drawback of 5.3.
> 
> Any idea how this can be resolved?
> 
> Best regards,
> Rob.
> 
> 
> 		
> __________________________________ 
> Do you Yahoo!? 
> Yahoo! Mail - Helps protect you from nasty viruses. 
> http://promotions.yahoo.com/new_mail
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
> 
> 



More information about the freebsd-stable mailing list