From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 13:07:14 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 E53B516A4CF for ; Thu, 5 Feb 2004 13:07:14 -0800 (PST) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98E1343D7D for ; Thu, 5 Feb 2004 13:06:45 -0800 (PST) (envelope-from kirk@strauser.com) Received: from pooh.strauser.com (pooh.honeypot.net [10.0.5.128]) by kanga.honeypot.net (8.12.10/8.12.10) with ESMTP id i15L5N7m093346; Thu, 5 Feb 2004 15:06:23 -0600 (CST) (envelope-from kirk@strauser.com) To: Damian Gerow 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> From: Kirk Strauser Date: Thu, 05 Feb 2004 15:05:17 -0600 In-Reply-To: <20040205203316.GB11717@afflictions.org> (Damian Gerow's message of "Thu, 5 Feb 2004 15:33:16 -0500") Message-ID: <87ekt9b5ki.fsf@strauser.com> Lines: 15 X-Mailer: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65', clamav-milter version '0.60p' cc: freebsd-current@freebsd.org 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:07:15 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable At 2004-02-05T20:33:16Z, Damian Gerow writes: > 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. =2D-=20 Kirk Strauser --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAIrAS5sRg+Y0CpvERAmdPAKChweM8Ny0RhJf2QQvjhsr/GeVOZQCfVuVE d0TQw8wse2PXPYvLIfUMZC8= =ilcY -----END PGP SIGNATURE----- --=-=-=--