Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Mar 2003 10:52:04 -0500 (EST)
From:      Bryan Liesner <bleez@verizon.net>
To:        Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: panic on boot (devfs_find) 
Message-ID:  <20030314103535.K605@gravy.kishka.net>
In-Reply-To: <6299.1047650191@critter.freebsd.dk>
References:  <6299.1047650191@critter.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030314103535.K605>