Date: Fri, 3 Sep 1999 16:37:14 +0930 From: Greg Lehey <grog@lemis.com> To: Greg Skafte <skafte@worldgate.com> Cc: freebsd-stable@freebsd.org Subject: Re: Vinum Kernel panic Message-ID: <19990903163713.K95378@freebie.lemis.com> In-Reply-To: <19990902234148.A74752@valis.worldgate.ca>; from Greg Skafte on Thu, Sep 02, 1999 at 11:41:48PM -0600 References: <19990902234148.A74752@valis.worldgate.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 2 September 1999 at 23:41:48 -0600, Greg Skafte wrote:
> I just cvsuped Freebsd RELENG_3 this evening and vinum cause the following:
>
> Kernel Panic Fatal trap 12 page Fault while in kernel mode
> Fault Virtual address= 0x10
> Fault Code = supervisor read, page not present
> Instruction Pointer = 0x8:0xc128a8bb
> Stack Pointer = 0x10: 0xcc1e5c40
> Frame Pointer = 0x10: 0xcc1e5c94
> Code Segment = base 0x0, limit 0xffff, type 0x1b
> = DPL 0, pres 1, def 321, gran 1
> Processor eflags = int enabled, resume IOPL 0
> Current Process = 16 (vinum)
> interupt mask =
> trap number = 12
> Panic: page fault
>
> ----------------------Kerenel conf --------------------------
The kernel config file isn't interesting.
> ----------- vinum config
> # Vinum configuration of nemisis.worldgate.ca, saved at Thu Sep 2 23:26:02 1999
> drive usr1 device /dev/wd0f
> drive home1 device /dev/wd0g
> drive usr2 device /dev/wd2s2f
> drive home2 device /dev/wd2s2g
> volume usr
> volume home
> plex name usr.p0 org striped 512b vol usr
> plex name home.p0 org concat vol home
> plex name home.p1 org concat vol home
> sd name usr.p0.s0 drive usr1 plex usr.p0 len 2095104b driveoffset 265b plexoffset 0b
> sd name usr.p0.s1 drive usr2 plex usr.p0 len 2095104b driveoffset 265b plexoffset 512b
> sd name home.p0.s0 drive home1 plex home.p0 len 3194880b driveoffset 265b plexoffset 0b
> sd name home.p1.s0 drive home2 plex home.p1 len 3194880b driveoffset 265b plexoffset 0b
That's not too unusual either.
> I pulled
> /* $Id: v.c,v 1.4.2.3 1999/05/05 05:11:14 grog Exp $ */
> and
> /* $Id: vinum.c,v 1.7.2.3 1999/05/05 05:15:37 grog Exp $
>
> etc from a back up and am having no issues.
That may or may not be related. Is this reproducible? Under what
circumstances? Are you using soft updates? We've seen one case that
fits that bill, but it doesn't look quite like yours, and it hasn't
shown up in -STABLE yet.
To quote vinum(4):
DEBUGGING PROBLEMS WITH VINUM
Solving problems with vinum can be a difficult affair. This section sug-
gests some approaches.
...
Kernel Panics
In order to analyse a panic which you suspect comes from vinum you will
need to build a debug kernel. See the online handbook for more details
of how to do this.
Perform the following steps to analyse a vinum problem:
1. Copy the files /usr/src/sys/modules/vinum/.gdbinit.crash,
/usr/src/sys/modules/vinum/.gdbinit.kernel,
/usr/src/sys/modules/vinum/.gdbinit.serial,
/usr/src/sys/modules/vinum/.gdbinit.vinum and
(etc)
I'm not going to repeat the whole man page here. You have it on your
system.
In view of the impending release of 3.3, I'm very interested in
following up on this one. But I'm going to need more information from
you.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990903163713.K95378>