Date: Wed, 6 Jun 2001 20:06:58 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: John Baldwin <jhb@FreeBSD.ORG> Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Possible VM patch.. Message-ID: <15134.50594.255478.53415@grasshopper.cs.duke.edu> In-Reply-To: <XFMail.010606170002.jhb@FreeBSD.org> References: <15134.49536.206316.481220@grasshopper.cs.duke.edu> <XFMail.010606170002.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin writes: > > I just got a panic on my UP machine. This one is a very weird panic that is > only triggered when the witness code gets its internal per-process lock lists > out of sync. I wish it was easier to trigger. It may be a witness bug or it > may be some sort of data corruption. :( The NULL vm_object panic in > vm_fault1() that I'm getting on the dual Rawhide seems fairly reproducible, so > I've added in a bunch of KTR tracepoints to see if I can narrow it down. This seems to happen to me regardless of whether or not I have witness enabled. The kernel I just tried did not have WITNESS. I've just kicked off another buildworld with an SMP kernel so my assert might trigger. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15134.50594.255478.53415>