Date: Sun, 16 Jul 2000 11:04:31 -0600 From: Warner Losh <imp@village.org> To: Thomas Faehnle <tf@wurbl.wn.bawue.de> Cc: grog@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/18685: "vinum start" under load causes "Fatal trap 12" Message-ID: <200007161704.LAA54343@harmony.village.org> In-Reply-To: Your message of "Sun, 16 Jul 2000 15:10:12 %2B0200." <E13DoQ1-0003rW-00@wurbl.bk.int> References: <E13DoQ1-0003rW-00@wurbl.bk.int>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <E13DoQ1-0003rW-00@wurbl.bk.int> Thomas Faehnle writes: : 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. I think that it is a vinum problem then. You got the crash dump at exactly the same location (inside of dscheck) as before? : > 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. Ah. OK. The first one shouldn't be impacted by this fix. I'll be happy to talk to grog about this, if it will help. Time to go back and change the bug -> feedback. Warner 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?200007161704.LAA54343>