From owner-freebsd-stable@FreeBSD.ORG Tue Feb 15 07:07:23 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9DEC16A4CE for ; Tue, 15 Feb 2005 07:07:23 +0000 (GMT) Received: from web54010.mail.yahoo.com (web54010.mail.yahoo.com [206.190.36.234]) by mx1.FreeBSD.org (Postfix) with SMTP id 316A743D4C for ; Tue, 15 Feb 2005 07:07:23 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: (qmail 44057 invoked by uid 60001); 15 Feb 2005 07:07:22 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=1XASLnCAl0T0A1Psq8jOqjUhNckZ4H/249keLi4ReNuzApSrKZDrhFeygIKe+xtGxsTrfBpYZQfn0l3RqYiBWck5lk9+d93QuA1ctnY8gQs9jgQsjOSWS4dgwjVeEOerDg0WXN2Ikqx9lspGKS+iAHH0FAVt1xI+1vGcnem1h4M= ; Message-ID: <20050215070722.44055.qmail@web54010.mail.yahoo.com> Received: from [147.46.44.181] by web54010.mail.yahoo.com via HTTP; Mon, 14 Feb 2005 23:07:22 PST Date: Mon, 14 Feb 2005 23:07:22 -0800 (PST) From: Rob To: Mark Kirkwood In-Reply-To: <420ECE69.9060006@paradise.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-stable@freebsd.org Subject: Re: atapci VIA 82C596B UDMA66 controller: problem for 5.X ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 07:07:23 -0000 --- Mark Kirkwood 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 error=84 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