From owner-freebsd-current Fri Mar 14 7:52: 9 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADBD037B401 for ; Fri, 14 Mar 2003 07:52:07 -0800 (PST) Received: from out003.verizon.net (out003pub.verizon.net [206.46.170.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 684AF43F85 for ; Fri, 14 Mar 2003 07:52:06 -0800 (PST) (envelope-from bleez@verizon.net) Received: from gravy.kishka.net ([151.197.249.111]) by out003.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20030314155205.ZRFI3697.out003.verizon.net@gravy.kishka.net>; Fri, 14 Mar 2003 09:52:05 -0600 Received: from localhost (localhost [127.0.0.1]) by gravy.kishka.net (8.12.8/8.12.8) with ESMTP id h2EFq46p000623; Fri, 14 Mar 2003 10:52:04 -0500 (EST) (envelope-from bleez@verizon.net) Date: Fri, 14 Mar 2003 10:52:04 -0500 (EST) From: Bryan Liesner X-X-Sender: root@gravy.kishka.net To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic on boot (devfs_find) In-Reply-To: <6299.1047650191@critter.freebsd.dk> Message-ID: <20030314103535.K605@gravy.kishka.net> References: <6299.1047650191@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [151.197.249.111] at Fri, 14 Mar 2003 09:52:05 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 14 Mar 2003, Poul-Henning Kamp wrote: > In message <20030314075657.E1432@gravy.kishka.net>, Bryan Liesner writes: > > > > > >I made posts here recently describing some panics which are somehow > >related to disappearing/never created device nodes. I am unable to > >produce a core dump at all, as it panics before / is mounted. > >The documented kern.dumpdev (unknown oid) doesn't exist and > >setting dumpdev=ad0s1b in loader.conf doesn't help either. > > Do you have any indication which device may be causing this ? I suspect /dev/null. On 3/11, I had a kernel compiled that was acting strangely. It would appear to run just fine, but when I went to compile, the build process complained that /dev/null doesn't exist. I checked, and it didn't. I also lost /dev/stderr when I looked at the nightly maintenance output. stdout and others just disappeared. X wouldn't start, complaining that vga didn't exist. (this happend shortly after I successfully ran X, exited, and restarted.) I was able to get a kernel up and running (strangely) on 3/12, but commits after that cause an immediate panic as soon as init starts. If I build a kernel from sources cut off at 3/10/2003 at 12:00, everything works fine. -- ========================================================== = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@verizon.net Home of the Gipper = ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message