Date: Sun, 12 Oct 1997 15:39:10 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Khetan Gajjar <khetan@iafrica.com> Cc: hackers@FreeBSD.ORG Subject: Re: Problem with 2.2.2-RELEASE machine Message-ID: <Pine.BSF.3.95.971012153423.8700H-100000@current1.whistle.com> In-Reply-To: <Pine.BSF.3.96.971013002228.24087U-100000@chain>
next in thread | previous in thread | raw e-mail | index | archive | help
try compiling with option DIAGNOSTIC with a new 2.2.x kernel (you should only need to grab a new kernel tree) I have a test in the generic 2.2.x kernel that looks for this. (alternatively, simply grab kern_synch.c from the web site and put in the DIAGNOSTIC section of tsleep() to your own kernel tree and recompile. (if you leave out the #if DIAGNOSTIC you can just recompile that file) do you know what make of processor you have? It may be that this is only on 486DX4 machines. julian On Mon, 13 Oct 1997, Khetan Gajjar wrote: > On Sun, 12 Oct 1997, Julian Elischer wrote: > > >Audience upgraded to hackers.. > > Kewl :-) > > >re: a panic at 0xf01b0384B > >it's in nortqr.. > >This is excactly the problem I see in 2.2 based machines. > >we have MANY in the field and occasioanally get hit by this. > > I get hit by this roughly every 20-30 days. Doesn't look good for > the stability, when other boxes stay up for months :-( > > >I've been looking for this for more than a month and have not been able > >to reproduce it, It just happens randomly out in the field. > > Noticed that too. Nothing specific sets it off. The worst kind > of error - non-reproducable. > --- > Khetan Gajjar - whois kg1779 | khetan@iafrica.com or khetan@os.org.za > http://chain.iafrica.com/~khetan | PGPKey : finger khetan@chain.iafrica.com > UUNET Internet Africa Support | FreeBSD enthusiast-www2.za.freebsd.org > Unix is user friendly; it's just selective about who it calls a friend! > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.971012153423.8700H-100000>