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!natinst.com!hrd769.brooks.af.mil!hrd769.brooks.af.mil!not-for-mail From: burgess@hrd769.brooks.af.mil (Dave Burgess) Newsgroups: comp.os.386bsd.questions Subject: Re: Sorry, I lost the 'drive light on and locked' patch. Date: 23 Jul 1993 08:54:59 -0500 Organization: Armstrong Laboratory, Brooks AFB, TX Lines: 37 Message-ID: <22oqk1$8f@hrd769.brooks.af.mil> References: <22gd69$6j3@hrd769.brooks.af.mil> <22helq$qe6@pdq.coe.montana.edu> <22hu06$kr@moritz.in-berlin.de> <22jja0$b1@hrd769.brooks.af.mil> NNTP-Posting-Host: hrd769.brooks.af.mil In article <22jja0$b1@hrd769.brooks.af.mil> I said: > >Bad news; it doesn't work for me either. All I needed to do was start >up gcc2 in the /usr/src/bin/sh directory (running from make in /usr/src) > and it would fail within seconds. > >Theo Deraadt suggested I turn on the WDCDELAY debug flag. It is showing >6200 millisecs for reset time (CONSISTENTLY). By my calculations, that >is about six seconds. > >The odd part there is that it will report one of these every second. > >Color me confused. > All right... I made Theo's suggested change. It made the problem go away for about three days. Once my confidence was up, I started trying to get the system back up to date. Something in gcc2 triggers the bug. It is getting to the point that I can't even build a new kernel to fix this persistent problem. Oh well. Another thing that seems to trigger the bug is writing a core.* file. The multirecord write problem seems to be the culprit. It is certainly a problem with timing. The 6 second time-out once a second still has me puzzled, and I suspect that is ALSO part of the problem. -- ------ TSgt Dave Burgess NCOIC AL/Management Information Systems Office Brooks AFB, TX