From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 13:16:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 461A416A4CE for ; Thu, 5 Feb 2004 13:16:38 -0800 (PST) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61D1043D5F for ; Thu, 5 Feb 2004 13:16:15 -0800 (PST) (envelope-from dgerow@afflictions.org) Received: from dementia.afflictions.org (dementia [172.16.0.56]) by pandora.afflictions.org (Postfix) with ESMTP id 494125D55B for ; Thu, 5 Feb 2004 16:45:20 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 462A26D42B; Thu, 5 Feb 2004 16:16:14 -0500 (EST) Date: Thu, 5 Feb 2004 16:16:14 -0500 From: Damian Gerow To: freebsd-current@freebsd.org Message-ID: <20040205211614.GE11717@afflictions.org> References: <20040126035539.GP1456@sentex.net> <20040127162251.GA90882@afflictions.org> <87oesdcqcd.fsf@strauser.com> <20040205192132.GA11676@afflictions.org> <87brodco8c.fsf@strauser.com> <20040205203316.GB11717@afflictions.org> <87ekt9b5ki.fsf@strauser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ekt9b5ki.fsf@strauser.com> X-Operating-System: FreeBSD 5.2-RC on a i386 X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.5.1i Subject: Re: -CURRENT barfing on UDMA on Via 8233 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2004 21:16:38 -0000 Thus spake Kirk Strauser (kirk@strauser.com) [05/02/04 16:05]: : > I'm just finishing up a level 0 dump of all filesystems, and I'm running : > pretty stable. This isn't surprising, and it's in line with what you saw : > -- running under PIO4 is stable, UDMA100 is not. : > : > Would it be worth it to try to force the system into UDMA66 or UDMA33? : : Well, it's certainly easy enough to experiment. Use atacontrol's "mode" : command to set whatever mode you'd like. Try UDMA33 and hit the drive(s) as : hard as you can. If you don't get errors, bump it up to UDMA66 and try : again. Yeah, I started doing that shortly after I sent the mail. I started at UDMA100, as that's where I know my problem is. A dump is zipping along just fine right now. I have a real job to attend to right now, so I'll pay a bit more attention to it later this evening.