From owner-freebsd-current Sun Jan 7 10:38:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA29260 for current-outgoing; Sun, 7 Jan 1996 10:38:38 -0800 (PST) Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA29252 for ; Sun, 7 Jan 1996 10:38:36 -0800 (PST) Received: (from vince@localhost) by apollo.COSC.GOV (8.7.3/8.6.9) id KAA07789; Sun, 7 Jan 1996 10:36:03 -0800 (PST) Date: Sun, 7 Jan 1996 10:36:03 -0800 (PST) From: -Vince- To: Stefan Esser cc: freebsd-current@freebsd.org Subject: Re: -current kernel problems In-Reply-To: <199601071816.AA11315@Sysiphos> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Sun, 7 Jan 1996, Stefan Esser wrote: > On Jan 7, 10:00, -Vince- wrote: > } Subject: Re: -current kernel problems > } On Sun, 7 Jan 1996, Stefan Esser wrote: > } > } > Hmm, well, I remember saying that sysctl has > } > problems on /your/ machine ... > } > > } > I also said, that there are ongoing changes > } > in that area ... > } > > } > In general, it seems to work just fine. And I > } > get more and more the impression, that you have > } > rebuilt a kernel from incompatible parts ... > } > > } > But the "sysctl -w kern.bootfile=/kernel.old" > } > which fails on your system is unneccesary anyway, > } > if you are going to reboot immediately. And you > } > just should rebuild /usr/sbin/config, configure > } > your kernel using the new binary, and then build > } > a kernel in a clean compile directory. > } > } Hmmm, the first time, I always do a kernel compile in a clean > } compile directory since I will always rm -rf /usr/src/sys/compile/ASTRO > } after every kernel compile and I did do the make world before the kernel > } compile so that should have rebuild the /usr/sbin/config binary and I > } even rm -rf /usr/src and then resupped everything just to be sure. Is > > Ok. That sounds very convincing indeed ... :) > > } there a way to debug the problem since it can't even log it to the > } /var/log/messages file as everything is just core dumping. > > - Did you manage to install a more recent kernel ? Yep, and the same thing happens.... Someone else compiled a kernel with the same config on their machine but when I got it, it always panics and reboots since it can't mount the root partition. > - Do you use any LKM's ? > (A make world might fail to rebuild a LKM, and > the incompatible LKM from an earlier build might > be left alone in /lkm.) Hmmm, I never rmed any of the old /lkm's but what I did was to be sure since David told me about it, I just cd /usr/src/lkm and then did a make clean, make all, and then make install. > - Can you boot single user (enter "-s" at the "Boot: " > prompt, fsck the file systems and mount (r/o) your > /var partition ? Hmmm, this is one thing I haven't tried yet.... For some reason, the original -current kernel of 12/28/95 seemed to have messed up the root partition and deleted the entire /bin directory as well as the /stand directory, newer kernels seems to have deleted my /mnt directory but the latest ones just panic with the vm_fault and doesn't mess up my partition. I'm still on the 11/23/95 kernel now on a 1/4/96 -current system so I'm not sure what really is the problem since it seems like it's something with the memory but it worked fine with everything up to 11/23/95. Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin - http://www.COSC.GOV/~vince UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan/Priscilla Chan Fan Club Mailing Lists Admin