Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 12 Feb 2005 09:01:29 -0800 (PST)
From:      Rob <spamrefuse@yahoo.com>
To:        freebsd-stable@freebsd.org
Cc:        markir@paradise.net.nz
Subject:   Re: atapci VIA 82C596B UDMA66 controller: problem for 5.X ?
Message-ID:  <20050212170129.28858.qmail@web54007.mail.yahoo.com>

next in thread | raw e-mail | index | archive | help
Mark Kirkwood wrote:
> 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?

At initial bootup, I get some UDMA error messages,
several lines with something like:

  READ_DMA UDMA ... ICRC error ... LBA....

then the kernel panics and the system reboots;
the same error messages occur again etc. etc.
ad infinitum.

> With respect to attempting a fix, you could try
> $ atacontrol mode 0 UDMA66 UDMA66

I have put this into the file '/etc/rc.early',
and that works. So then, after bootup, I get:

  # sysctl hw.ata.ata_dma
  hw.ata.ata_dma: 0
  # atacontrol mode 0
  Master = UDMA66
  Slave  = BIOSPIO


What does that mean? UDMA66 and hw.ata.ata_dma=0 ?

And why then is UDMA66 not automatically choosen
at bootup?

Thanks,
Rob.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050212170129.28858.qmail>