Date: Thu, 5 Feb 2004 16:16:14 -0500 From: Damian Gerow <dgerow@afflictions.org> To: freebsd-current@freebsd.org Subject: Re: -CURRENT barfing on UDMA on Via 8233 Message-ID: <20040205211614.GE11717@afflictions.org> In-Reply-To: <87ekt9b5ki.fsf@strauser.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040205211614.GE11717>