Date: Tue, 03 Oct 2000 11:12:11 +0200 From: Mark Murray <mark@grondar.za> To: Jason Evans <jasone@canonware.com> Cc: freebsd-smp@FreeBSD.ORG Subject: Re: witness code status? Message-ID: <200010030912.e939CDL06411@grimreaper.grondar.za> In-Reply-To: <20001002164139.I58256@canonware.com> ; from Jason Evans <jasone@canonware.com> "Mon, 02 Oct 2000 16:41:39 MST." References: <20001002164139.I58256@canonware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I (and others) have been running kernels with the witness code enabled for
> over a month. The witness code's purpose is to detect lock cycles that
> could cause deadlock, among other incorrect mutex uses. The stack trace
> and panic message in your email seem indicate a programming error. In
> other words, the witness code is doing its job.
Jason,
I'd like to ask your help on this; It seems that turning WITNESS on causes
the /dev/random driver to screw up royally.
I thought I was quite careful about that. Now, I'm a bit out of my depth.
Could you give me a hand?
M
>
> Jason
>
> > panic: mutex_enter: MTX_DEF on MTX_SPIN mutex random harvest\
> > @/usr/src/sys/modules/randomdev/../../dev/randomdev/yarrow.c:515
> > cpuid = 1; lapic.id = 00000000
> Debugger("panic')
> >
> > CPU1 stopping CPUs: 0x00000001 stopped
> > Stopped at Debugger+0x38: movb $0,in_Debugger.684
> >
> > db>trace
> > Debugger(c0277da1)
> > panic
> > witness_enter
> > _mtx_enter
> > random_harvest_internal
> > write_random
> > random_write
> > ufs_vnoperatespec
> > vn_write
> > dofilewrite
> > write
> > syscall2
> > Xint0x80_syscall
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-smp" in the body of the message
>
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
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?200010030912.e939CDL06411>