*BSD News Article 18710


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: 21 Jul 1993 09:19:30 -0500
Organization: Armstrong Laboratory, Brooks AFB, TX
Lines: 40
Message-ID: <22jja0$b1@hrd769.brooks.af.mil>
References: <22gd69$6j3@hrd769.brooks.af.mil> <22helq$qe6@pdq.coe.montana.edu> <22hu06$kr@moritz.in-berlin.de>
NNTP-Posting-Host: hrd769.brooks.af.mil

In article <22hu06$kr@moritz.in-berlin.de> berry@moritz.IN-Berlin.DE (Stefan Behrens) writes:
>In article <22helq$qe6@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes:
>>rm /dev/drum
>>touch /dev/drum
>>
>>(Maybe this should go in the FAQ. *grin*)
>
>Doesn't work for me. Would be to simple, wouldn't it? And I thought that
>the /dev/drum bug was fixed month ago?
>

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.

>Removing and touching /dev/drum doesn't change anything at all. I still
>can do a ``tar -cf /dev/null /usr2 & tar -cf /dev/null /usr1'' where
>/usr1 and /usr2 are nfs-mounted and after a few seconds the controller
>will hang...
>...and timeout with my code, and will be reset and the request will be
>restarted.
>

Please E-Mail me.  Please.  PLEASE.  PRETTY PLEASE.



-- 
------
TSgt Dave Burgess
NCOIC AL/Management Information Systems Office
Brooks AFB, TX