Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!darwin.sura.net!gatech!concert!sas!mozart.unx.sas.com!torpid.unx.sas.com!sastdr
From: sastdr@torpid.unx.sas.com (Thomas David Rivers)
Subject: Re: Corrupted directory
Sender: news@unx.sas.com (Noter of Newsworthy Events)
Message-ID: <Bw4Fv7.M4L@unx.sas.com>
Date: Wed, 14 Oct 1992 17:13:55 GMT
References: <24966.9210120127@thor.cf.ac.uk> <26947.9210120417@thor.cf.ac.uk> <1bd165INNrfe@iskut.ucs.ubc.ca>
Nntp-Posting-Host: torpid.unx.sas.com
Organization: SAS Institute Inc.
Lines: 25
Regarding this infinite reboot cycle; I recently applied the entire
beta patchkit (from a new, clean, installation of 386bsd 0.1) and
began getting this problem.
I.e. If I have to shut down for some reason, or the power goes out; the
machine reboots. Root gets fsck'd and repaired; and the
machine reboots again. Then there is another problem with the
fsck of root, and the machine reboots, etc... encountering the
same problem over and over.
I've now seen this happen on two machines to which I applied the beta
patchkit. It did *not* happen on these machines using the kernel I
had patched together from news articles. This means (at least to me)
there is some patch applied by the patchkit which I had not otherwise
applied in my kernel, that is causing the problem.
I've seen it on a SCSI disk and IDE disk, so I don't think it's in the
driver... could it be some of the changes to init.c?
- Dave R. -
(rivers@ponds.uucp (home))
(sastdr@unx.sas.com (work))
--
UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express