From owner-freebsd-current Thu Jun 15 22:32:14 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 19A2637BBB4 for ; Thu, 15 Jun 2000 22:32:12 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 12141 invoked from network); 16 Jun 2000 05:32:11 -0000 Received: from lc210.cvzoom.net (HELO cvzoom.net) (208.226.154.210) by ns.cvzoom.net with SMTP; 16 Jun 2000 05:32:11 -0000 Message-ID: <3949BBDA.24823CCE@cvzoom.net> Date: Fri, 16 Jun 2000 01:32:11 -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: The Hermit Hacker , 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 The Hermit Hacker wrote: > > On Thu, 15 Jun 2000, 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). > > okay, I see the same thing, but *believe* that this has to do with the > whole thread on ttyv0 that just passed through here, so am just waiting > and watching the commit logs for something that "looks" appropriate ... Well, I don't think that ttyv0 would be the problem in this case. See, the machine just hangs with a fatal trap immediately after the boot loader attempts to boot the kernel. The whole thread with ttyv0 seems to be an issue only when /etc/rc.conf is read. So, basically the page fault is occuring way at the beginning of the boot process long before the console driver is even loaded. 8-( - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message