Date: Thu, 05 Feb 2004 15:05:17 -0600 From: Kirk Strauser <kirk@strauser.com> To: Damian Gerow <dgerow@afflictions.org> Cc: freebsd-current@freebsd.org Subject: Re: -CURRENT barfing on UDMA on Via 8233 Message-ID: <87ekt9b5ki.fsf@strauser.com> In-Reply-To: <20040205203316.GB11717@afflictions.org> (Damian Gerow's message of "Thu, 5 Feb 2004 15:33:16 -0500") 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Transfer-Encoding: quoted-printable At 2004-02-05T20:33:16Z, Damian Gerow <dgerow@afflictions.org> 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----- --=-=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87ekt9b5ki.fsf>