Date: Tue, 22 May 2001 13:37:30 -0700 (PDT) From: John Baldwin <jhb@FreeBSD.ORG> To: Matthew Jacob <mjacob@feral.com> Cc: smp@FreeBSD.ORG Subject: RE: more recursive mutex panics- help me out with the One True w Message-ID: <XFMail.010522133730.jhb@FreeBSD.org> In-Reply-To: <Pine.LNX.4.21.0105221131160.10376-100000@zeppo.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22-May-01 Matthew Jacob wrote: > > After overnight run, I got: > > isp1: kthread up release simq > lrecursed on non-recursive lock (sleep mutex) process lock @ > ../../kern/kern_lock.c:262 > first acquired @ ../../kern/kern_sig.c:447 > panic: recurse > panic > Stopped at That doesn't seem to be from any problems in your code. I'm somewhat curious why lockmgr is being called during a signal operation however, as that seems to be the problem you've run into. I'd need a backtrace to be more certain however. > So- 2 questions: > > > 1. Are the defines for grabbing/releasing Giant acceptable in kthread > context? They look fine. > 2. Is the msleep on lbolt a bad idea? The msleep is fine, the &lbolt part I'm not an expert on, so I'm not sure if it is evil or not. :) > -matt -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.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?XFMail.010522133730.jhb>