e is of no help, mailing list
archives have no mention of this. This is on an existing 4.0-2214
system, kernel is 5.0-C as of 2 days ago.
--
Marius Strom <[EMAIL PROTECTED]>
Professional Geek/Unix System Administrator
Alpha1 Internet <http://www.alpha1.net>
http://www.marius.org
mpletely hung. Other people could get it because they had other drives
to write logging information too when the UDMA drive was locked.
---
Marius Strom <[EMAIL PROTECTED]>
Professional Geek/Unix System Administrator
Alpha1 Internet <http://www.alpha1.net>
http://www.marius.org/mariu
archived where I can find it.
Seems to only happen with the ata driver, IIRC.
--
Marius Strom <[EMAIL PROTECTED]>
Professional Geek/Unix System Administrator
Alpha1 Internet <http://www.alpha1.net>
http://www.marius.org/marius.pgp 0x42C74CBA *UPDATED PGP KEY 2/24/2000*
In theory, there
roller and
put them on the Standard UDMA33 controllers, and it should clear things
up.
--
Marius Strom <[EMAIL PROTECTED]>
Professional Geek/Unix System Administrator
Alpha1 Internet <http://www.alpha1.net>
http://www.marius.org/marius.pgp 0x42C74CBA *UPDATED PGP KEY 2/24/2000*
Mine's a Western Digital WD205BARTL (Caviar 20.5 gig 7200 RPM)
--
Marius Strom <[EMAIL PROTECTED]>
Professional Geek/Unix System Administrator
Alpha1 Internet <http://www.alpha1.net>
http://www.marius.org/marius.pgp 0x5645C228
In theory, there is no difference between th
Hans and others,
I have the same situation - happy to get a new motherboard and processor,
unhappy to hang FreeBSD. My situation is different, however - I'm running
single processor currently and it still hangs. I've also experienced this
issue with and without softupdates.
--
Ma
