From owner-freebsd-current Sun Jan 7 10:21:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA27303 for current-outgoing; Sun, 7 Jan 1996 10:21:56 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA27183 for ; Sun, 7 Jan 1996 10:20:52 -0800 (PST) Received: by Sysiphos id AA11315 (5.67b/IDA-1.5 for freebsd-current@freebsd.org); Sun, 7 Jan 1996 19:16:47 +0100 Message-Id: <199601071816.AA11315@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Sun, 7 Jan 1996 19:16:47 +0100 In-Reply-To: -Vince- "Re: -current kernel problems" (Jan 7, 10:00) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: -Vince- Subject: Re: -current kernel problems Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk 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 ? - 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.) - Can you boot single user (enter "-s" at the "Boot: " prompt, fsck the file systems and mount (r/o) your /var partition ? Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se