Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!uwm.edu!wupost!cs.utexas.edu!swrinde!gatech!destroyer!cs.ubc.ca!alberta!cpsc.ucalgary.ca!ajfcal!novatel!hpeyerl From: hpeyerl@novatel.cuc.ab.ca (Herb Peyerl) Subject: Non-Newbie (oldbie) has problems with patchkit. Message-ID: <1992Oct22.151446.12339@novatel.cuc.ab.ca> Organization: none Date: Thu, 22 Oct 1992 15:14:46 GMT Lines: 58 OK; color me humiliated... The other day I thought I'd reinstall 0.1 on my home-system since it was getting kind of messy (had some of my own patches/kludges in it and a variety of other foul-ups)... So, I low-leveled the disk, created a 1 meg dos partition, and installed via Lynne's install procedure... I then created my own /sys/i386/conf/<HOSTNAME> file (basically a GENERICISA with we, ne, is, as, and sl drivers excluded); config'd, and rebuilt the kernel. I rebooted and the new kernel worked fine. Then I installed Terry's fine patchkit and installed all of the patches... Finally, last night I rebuilt the kernel and tried to boot off it... "Panic: can't mount root" or some such thing. Infinite reboot cycle. Another thing it says (I can only read so much in the 1.2ms between the time the message pops up and it clears the screen) is something about "Error reading DOS partition" or some such... I can't quite recall... So, boot off the fixit.fs; fsck, mount, mv 386bsd.old 386bsd, umount, and reboot... Everything's fine again... I dug through the Patchkit INDEX and noticed that the only seemingly relative patch was 00006 (chroot fix) so after digging through vfs_lookup.c, I found that the patch was installed correctly... I put a printf() right before the panic() a few lines up thinking maybe that was it... But it's not... Anyways, am I missing something here? Also, there appears to be sort of a generic problem with my machine in general... At work (here) I have 386bsd on a Maxtor 4380E with a WD1007 and it appears VERY stable... At home, I use a WD1006 (RLL) controller and either one of two drives (Maxtor 1140 or Micropolis 1335) and for some reason, it appears REALLY unstable... If, for example, I do something to cause the system to go down (turn off the power, three fingered salute, etc), then an fsck will cause the system to hang after reporting summary information... (by hang, I mean, caps-lock doesn't cause any change of lights.. 3 fingered salute doesn't respond.) The only thing that works is physically turning the machine off (don't have a reset button). It then takes about 3 or 4 attempts to reboot the machine before it will pass by fsck and work... If I boot off the fixit.fs, and fsck from there, it still may not boot (unless I do a "touch /fastboot) without hanging... I just can't figure it out since I can't always recreate the circumstances... I was hoping that by installing all the patches, it would solve this problem... hence......... Oh, yeah.. When I mount the /dev/wd0a from the fixit disk, it says: "warning: /dev/wd0a overlaps partition c" or some such thing but all appears normal... Oh, for information sake, at home I have an Intel 386-16 motherboard (with very OLD phoenix bios; like it matters), the DX processor, 8.5 MB RAM, Maxtor 1140, WD1006, 3c503, etc.... Any comments anyone? -- "I was early to finish | hpeyerl@novatel.cuc.ab.ca <Reply-To> | I brew | I was late to start, I | peyerlh@cuug.ab.ca | there- | might be an adult, but | #define JANITOR "Network Administrator"| fore I | I'm a minor at heart." | JANITOR, NovAtel Communications Ltd.| AM. |