Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Jul 2000 11:07:31 +0930
From:      Greg Lehey <grog@lemis.com>
To:        Thomas Faehnle <tf@wurbl.wn.bawue.de>
Cc:        imp@freebsd.org, freebsd-bugs@freebsd.org
Subject:   Re: kern/18685: "vinum start" under load causes "Fatal trap 12"
Message-ID:  <20000717110731.J57098@wantadilla.lemis.com>
In-Reply-To: <E13DoQ1-0003rW-00@wurbl.bk.int>
References:  <200007110609.XAA73608@freefall.freebsd.org> <E13DoQ1-0003rW-00@wurbl.bk.int>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 16 July 2000 at 15:10:12 +0200, Thomas Faehnle wrote:
> On 10 Jul, imp@freebsd.org wrote:
>> Synopsis: "vinum start" under load causes "Fatal trap 12"
>>
>> State-Changed-From-To: feedback->closed
>> State-Changed-By: imp
>> State-Changed-When: Tue Jul 11 00:07:07 MDT 2000
>> State-Changed-Why:
>> This looks EXACTLY like a bug that I've fixed in subr_disk.c.  Likely
>> they are related.
>
> No go. I did an update yesterday (version id of subr_disk.c is
> $FreeBSD: /ctm/FreeBSD/anoncvs/cvs/src/sys/kern/subr_disk.c,v
>  1.20.2.1 2000/07/11 06:02:49 imp Exp $), but nothing changed. Crash
> dump avail on request.
>
>> it would be even more likely if the vinum start was
>> not the first time you did this, but the second or theird because
>> disk_destroy was leaving bogons around.
>
> I often get that crash on the first "vinum start", provided the machine
> is somewhat loaded and there is some disk activity going on.

Could you please read http://www.lemis.com/vinum/how-to-debug.html and
give me the dump backtrace information according to the instructions
there?

Thanks
Greg
--
Finger grog@lemis.com for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




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