Date: Fri, 14 Mar 2003 11:26:45 -0600 From: Krzysztof Parzyszek <kristof@swissmail.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: walt <wa1ter@myrealbox.com>, freebsd-current@FreeBSD.ORG Subject: Re: GEOM_MBR breaks my kernel Message-ID: <20030314172645.GA91658@antares.student.iastate.edu> In-Reply-To: <6592.1047652673@critter.freebsd.dk> References: <3E71E323.5010808@myrealbox.com> <6592.1047652673@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 14, 2003 at 03:37:53PM +0100, Poul-Henning Kamp wrote:
> In message <3E71E323.5010808@myrealbox.com>, walt writes:
> >I've been unable to boot any kernel I've built since about March 11
> >and I've narrowed it down to the GEOM_MBR option.
> >
> >With GEOM_MBR I get a kernel page fault error when trying to
> >mount the root filesystem at boot time.
>
> Can you get us the messages and a traceback ?
I saw the same thing on my system. I don't have the exact message
or traceback around, but the problem was essentially a null pointer
dereference while in kernel mode.
I was able to locate the offending line in the source:
In devfs_allocv:
if (de->de_dirent->d_type == DT_CHR) {
dev = *devfs_itod(de->de_inode);
if (dev == NULL)
return (ENOENT);
} else {
...
The first comparison causes the problem, since de->de_dirent == NULL.
The problem did not exist until I turned WITNESS & INVARIANTS off
(in a kernel with all GEOM_* stuff enabled).
Let me know if you need more information. If you need the traceback,
I'd appreciate if you told me how to get it written to a file. :)
Krzysztof
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?20030314172645.GA91658>