From owner-freebsd-stable@FreeBSD.ORG Sat Feb 12 17:01:32 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 1A21B16A4CE for ; Sat, 12 Feb 2005 17:01:32 +0000 (GMT) Received: from web54007.mail.yahoo.com (web54007.mail.yahoo.com [206.190.36.231]) by mx1.FreeBSD.org (Postfix) with SMTP id 7F99F43D41 for ; Sat, 12 Feb 2005 17:01:31 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: (qmail 28860 invoked by uid 60001); 12 Feb 2005 17:01:29 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=6Wvj1C3mr/R3hEhK2Mnz5DkCK948EjbnkoKs6QIJrou5y5g15eDUHcmKaxnZPg3yn8FNqN8r25MiU2JFa9NoT0kXSCBDpCpaHtUkn4V3E76Ig/BPVe7rwgcURq9OsJFXuu2muUOd9fDw1PHgNs/vNKtrFwTDeVh/ElrxI6LXMe4= ; Message-ID: <20050212170129.28858.qmail@web54007.mail.yahoo.com> Received: from [147.46.44.181] by web54007.mail.yahoo.com via HTTP; Sat, 12 Feb 2005 09:01:29 PST Date: Sat, 12 Feb 2005 09:01:29 -0800 (PST) From: Rob To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: markir@paradise.net.nz 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: Sat, 12 Feb 2005 17:01:32 -0000 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: 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 [38792/16/63] > at ata0-master UDMA66 > ad1: 19092MB [38792/16/63] > at ata0-slave UDMA66 > acd0: CDRW > 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