From owner-freebsd-current Fri Jun 16 5:28:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.152.mpoweredpc.net [142.177.193.152]) by hub.freebsd.org (Postfix) with ESMTP id CAFF837BE2E for ; Fri, 16 Jun 2000 05:28:47 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id JAA24129; Fri, 16 Jun 2000 09:27:36 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 16 Jun 2000 09:27:36 -0300 (ADT) From: The Hermit Hacker To: Donn Miller Cc: current@freebsd.org Subject: Re: -current kernel broken? In-Reply-To: <3949BBDA.24823CCE@cvzoom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG oops, sorry ... I wasn't even getting a page fault, it was just hanging. Hrmmm, maybe I'll try a newer kernel and see if it still exhibits the same problem ... my luck, I got my sources part way through someone's update :) On Fri, 16 Jun 2000, Donn Miller wrote: > 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 > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message