Date: Sun, 21 Aug 2011 18:34:23 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Andriy Gapon <avg@freebsd.org>, "Kenneth D. Merry" <ken@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: panic: mtx_lock_spin: recursed on non-recursive mutex cnputs_mtx @ /usr/src/sys/kern/kern_cons.c:420 when running dump in ddb Message-ID: <CAGH67wT8--206eD7HEa8zKEn=bTrUZDpCsNy0_9kS1u0ZAZ7Mg@mail.gmail.com> In-Reply-To: <CAGH67wSj8d9=oLmh5e68DoSwo5u7nTXL7LacHRcvymRbOf=rPg@mail.gmail.com> References: <CAGH67wSj8d9=oLmh5e68DoSwo5u7nTXL7LacHRcvymRbOf=rPg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 18, 2011 at 5:55 PM, Garrett Cooper <yanegomi@gmail.com> wrote:
> Hi,
> =A0 =A0Long story short, I was running a UP kernel on a netbook trying to
> stimulate a crash and when I did dump, it would periodically fail
> non-recursive mutex failure with the output shown below (I caught it
> once, but the other times the dump failed).
This actually shows up when generating a panic via boot -v with
WITNESS, so it's potentially a race condition on my laptop. Adding
MTX_RECURSE to the mutex object didn't help things either.
Thanks,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wT8--206eD7HEa8zKEn=bTrUZDpCsNy0_9kS1u0ZAZ7Mg>