*BSD News Article 22755


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!xlink.net!subnet.sub.net!flatlin!bad
From: bad@flatlin.ka.sub.org (Christoph Badura)
Subject: Re: NETBSD and freezing problems
Date: Fri, 22 Oct 1993 10:48:01 GMT
Message-ID: <CFAoo2.Kwo@flatlin.ka.sub.org>
References: <29n0in$446@darkstar.UCSC.EDU> <BLYMN.93Oct21202416@mallee.awadi.com.au>
Organization: Guru Systems/Funware Department
Lines: 22

In <BLYMN.93Oct21202416@mallee.awadi.com.au> blymn@mallee.awadi.com.au (Brett Lymn) writes:
>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.

It also seems that the hangs are somehow related to with whether one
uses NFS mounted filesystems or not.  Our NetBSD box has been pretty
stable since we stopped importing any NFS mounted filesystems.

Hmm. Maybe something with the interrupt and software interrupt code is
wrong and causes the system to lose a wd interrupt?

>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

I'll try.
-- 
Christoph Badura  ---  bad@flatlin.ka.sub.org  --  +49 721 606137

Wer soll denn die Automatik bedienen,
wenn die sich nicht per Funk melden.   -- Cliff Allistair McLane