From owner-freebsd-current Fri Jun 16 17:34:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id D20C437C2E7 for ; Fri, 16 Jun 2000 17:34:12 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 5445 invoked from network); 17 Jun 2000 00:34:06 -0000 Received: from lc210.cvzoom.net (HELO cvzoom.net) (208.226.154.210) by ns.cvzoom.net with SMTP; 17 Jun 2000 00:34:06 -0000 Message-ID: <394AC77E.88FB7D90@cvzoom.net> Date: Fri, 16 Jun 2000 20:34:06 -0400 From: Donn Miller X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Wes Morgan Cc: current@freebsd.org Subject: Re: -current kernel broken? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Morgan wrote: > > As of about 7pm EDT I can't boot a -current kernel. I _can_ boot a kernel > from the 13th I snagged from a snapshot kernel disk, and I can boot the > snapshot from the 15th (but since userconfig does not work the lnc device > spams so many error messages the system never reaches a prompt). > > Already did the make clean depend all install for /sys/boot/i386 and that > was no help. The kernel just freezes _right_ after trying to boot... I'm > not sure how far its getting, I'll have to play around with a debug kernel > and see what I can get from it (if anything). I saw this as well. It turns out the optimizations I was using when building my kernel was causing it. I was using -march=pentium -Os -pipe. Falling back to -O -pipe solved this. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message