Date: Sat, 11 Jan 2014 19:32:04 -0800 From: Sean Bruno <sean_bruno@yahoo.com> To: Adam McDougall <mcdouga9@egr.msu.edu> Cc: freebsd-stable@freebsd.org Subject: Re: panic: stable/10 with Debugging enabled in kern_cons.c:500 Message-ID: <1389497524.1395.1.camel@powernoodle.corp.yahoo.com> In-Reply-To: <52D208EF.1010601@egr.msu.edu> References: <1389478327.46758.7.camel@powernoodle.corp.yahoo.com> <1389480297.46758.9.camel@powernoodle.corp.yahoo.com> <52D208EF.1010601@egr.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2014-01-11 at 22:15 -0500, Adam McDougall wrote: > On 01/11/2014 17:44, Sean Bruno wrote: > > On Sat, 2014-01-11 at 14:12 -0800, Sean Bruno wrote: > >> I can't imagine that I'm the first person to run with the following > >> debug options enabled: > >> > >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html > >> > >> But, I can't get stable/10 to post on a plain old supermicro box with > >> those debugging symbols enabled. > >> > >> random: unblocking device. > >> panic: mtx_lock_spin: recursed on non-recursive mutex cnputs_mtx > >> @ /usr/src/sys/kern/kern_cons.c:500 > >> > > > > Witness induced. Removed the witness option and this doesn't happen > > (obviously). Can I get someone familiar with console code to look into > > this? Kind of crappy when I'm investigating a resource starvation > > issue. > > > > sean > > > > Confirmed panic in 10-r258899M (20131203) on XenServer. For reference, > what is your rev? Pretty close to top of tree stable/10 260555 sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1389497524.1395.1.camel>