Date: Mon, 2 Oct 2000 17:20:48 -0700 From: Jason Evans <jasone@canonware.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-smp@freebsd.org Subject: Re: witness code status? Message-ID: <20001002172048.J58256@canonware.com> In-Reply-To: <200010030011.e930Be940283@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Mon, Oct 02, 2000 at 05:11:40PM -0700 References: <20001002164139.I58256@canonware.com> <200010030011.e930Be940283@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 02, 2000 at 05:11:40PM -0700, Steve Kargl wrote: > > Shoot, I was afraid you's say the above. I haven't been able to > convince this machine to give me a crash dump for further analysis. > I'll keep trying because this repeatable here. > > The KDEBUG option isn't documented in NOTES, but I noticed it strewn > through kern_mutex.c. Will enabling this option provide more > information that can help track this done? Hmm, I don't know what KDEBUG is for. However, you should definitely define the SMP_DEBUG option if you haven't already. I've been building kernels for a while now with the following additional pertinent options: options INVARIANTS options INVARIANT_SUPPORT options DIAGNOSTIC options SMP_DEBUG options WITNESS As for not being able to get a crash dump, I've been using ddb/gdb, so I'm not of much help there. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001002172048.J58256>