Date: Mon, 14 Feb 2005 23:07:22 -0800 (PST) From: Rob <spamrefuse@yahoo.com> To: Mark Kirkwood <markir@paradise.net.nz> Cc: freebsd-stable@freebsd.org Subject: Re: atapci VIA 82C596B UDMA66 controller: problem for 5.X ? Message-ID: <20050215070722.44055.qmail@web54010.mail.yahoo.com> In-Reply-To: <420ECE69.9060006@paradise.net.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Mark Kirkwood <markir@paradise.net.nz> wrote:
> Rob wrote:
> >
> >
> > What does that mean? UDMA66 and hw.ata.ata_dma=0 ?
> >
> Hmmm, that is interesting, 2 suggestion to determine
> what is going on:
> - run diskinfo -t on your disks and let us know the
> results
Motherboard: LG, type LGM-VBX6
atapci0: VIA 82C596B UDMA66 controller
ad0: 43979MB IBM-DTLA-307045/TX6OA50C
In this case there's only one harddisk and when I do
# atacontrol mode 0 UDMA66 BIOSPIO
I get lots of such lines:
ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying
request) LBA=20185375
ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying
request) LBA=20185375
ad0: FAILURE - WRITE_DMA status=51<READY,DSC,ERROR>
error=84<ICRC,ABORTED> LBA=20185375
Until the PC completely freezes. A power on/off is
only cure then.
# diskinfo -t ad0
ad0
512 # sectorsize
46115758080 # mediasize in bytes (43G)
90069840 # mediasize in sectors
89355 # Cylinders according to firmware.
16 # Heads according to firmware.
63 # Sectors according to firmware.
Seek times:
Full stroke: 250 iter in 4.608205 sec =
18.433 msec
Half stroke: 250 iter in 5.438044 sec =
21.752 msec
Quarter stroke: 500 iter in 8.602828 sec =
17.206 msec
Short forward: 400 iter in 1.533293 sec =
3.833 msec
Short backward: 400 iter in 2.761972 sec =
6.905 msec
Seq outer: 2048 iter in 0.407381 sec =
0.199 msec
Seq inner: 2048 iter in 0.396248 sec =
0.193 msec
Transfer rates:
outside: 102400 kbytes in 19.370328 sec
= 5286 kbytes/sec
middle: 102400 kbytes in 19.378847 sec
= 5284 kbytes/sec
inside: 102400 kbytes in 19.379687 sec
= 5284 kbytes/sec
> - use sysctl to set hw.ata.ata_dma=1 and see what
> happens
Does this make sense if UDMA66 is not even working?
>
> At a guess I would suggest that dma is broken for
> your motherboards in 5.3 (what were they again?).
The report above is for LG (LGM-VBX6).
Is there a way to verify the status of my DMA ?
-----------------------------------
There's a second PC, with similar problems, which
I will report shortly:
Motherboard: Altos AL-6BV67
atapci0: VIA 82C596B UDMA66 controller
ad0: 76319MB WDC WD800JB-00CRA1/17.07W17
On this PC, I can set UDMA66, after bootup.
Haven't tried the "hw.ata.ata_dma=1" option yet.
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?20050215070722.44055.qmail>