From owner-freebsd-stable Sat Apr 1 10:55:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (ztown1-1-55.adsl.one.net [207.78.254.55]) by hub.freebsd.org (Postfix) with ESMTP id 2F51F37B993 for ; Sat, 1 Apr 2000 10:55:15 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id OAA11381; Sat, 1 Apr 2000 14:00:18 -0500 (EST) (envelope-from cokane) Date: Sat, 1 Apr 2000 14:00:18 -0500 From: Coleman Kane To: C J Michaels Cc: Coleman Kane , FreeBSD Stable Subject: Re: 4.0-S 3/31 KERNEL causes reboot on startup Message-ID: <20000401140018.B11341@evil.2y.net> References: <20000401005254.C6904@evil.2y.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from cjm2@earthling.net on Sat, Apr 01, 2000 at 09:31:58AM -0500 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm... you may want to check the gzipped, archived messages. Also you should probably turn on full debugging in your new kernel. I think it's: makeoptions "-g -DDEBUG" or something like that. You should also check /etc/make.conf to see what your CCOPTFLAGS is set to. I have had kernels that simply reboot the system when used with -O2 or -O3, I find that -O works fine. --cokane C J Michaels had the audacity to say: > > OK.. I booted with kernel.GENERIC and looked at /var/log/messages. There > were only boot messages from my last 2 attempts to boot from the > kernel.GENERIC even though I had tried booting the new kernel inbetween. > > Any other ideas? :P > -Chris > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message