Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!destroyer!news.itd.umich.edu!altitude From: altitude@css.itd.umich.edu (Alex Tang) Newsgroups: comp.os.386bsd.questions Subject: Re: NETBSD and freezing problems Date: 26 Oct 1993 00:26:21 GMT Organization: University of Michigan ITD/User Services Lines: 26 Message-ID: <2ahqrd$12l@terminator.rs.itd.umich.edu> References: <29n0in$446@darkstar.UCSC.EDU> <BLYMN.93Oct21202416@mallee.awadi.com.au> NNTP-Posting-Host: stimpy.css.itd.umich.edu X-Newsreader: TIN [version 1.2 PL1] Brett Lymn (blymn@mallee.awadi.com.au) wrote: : There are a few bugs that will cause the symptom you describe. One of : them was in the original wd.c drivers (I'm talking 0.1 here), they : trusted the hardware to do the right thing all the time, sadly this is : not the case on some machines when the disk activity rises. I did : make a fix for this under 386BSD 0.1, I do not know if the fix made it : into NetBSD. From what I understood a "better" version of the fix : (something about using kernel timeouts instead of the poll loop I : had). Can anyone using NetBSD confirm/deny this is fixed? What you : need to look for is some logic around the loops that check for the : controller/disk being busy in wdstart() that will reset and restart : the operation if the disk/controller stays busy for too long. : I do have a netbsd0.8 version of my patch that someone else ported for : me if anyone wants to try jamming it into netbsd0.9 Hi. I'd like these patches...PLEEEEEZZZZZEEEEEE....I'd really like it if my machine didn't crash so much on me. :( -- Alex Tang --- ALTITUDE@UMICH.EDU...USERW00Y@UMICHUM.BITNET -----------+ U of M, SNRE: Student and Computer Consultant II, PGP on req.| ITD/CSS Consultant, Short asian with long hair :)