Date: Mon, 23 Dec 2002 12:15:22 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: questions@FreeBSD.ORG Subject: Re: Kernel panic questions.. Message-ID: <20021223121522.GB15678@happy-idiot-talk.infracaninophi> In-Reply-To: <61BD3662-166C-11D7-AA90-003065715DA8@pursued-with.net> References: <200212231101.gBNB1OgQ005929@babelfish.pursued-with.net> <61BD3662-166C-11D7-AA90-003065715DA8@pursued-with.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 23, 2002 at 03:47:58AM -0800, Kevin Stevens wrote:
> In the last week I've gotten two kernel panics with reboot while
> compiling. The log message says:
>
> kernel log messages:
> refused
> panic: lockmgr: locking against myself
>
> Then it politely syncs disks and helpfully reboots. Any help with what
> a lockmgr is or why it is so unhappy?
That's a kernel internal function: it's probably something like the
kernel locking a device for exclusive access from a particular source,
and then finding that it's actually locked out the bit that was
requesting the lock.
That shouldn't happen. However, without a whole lot more information,
there's no way anyone can tell you what exactly has gone wrong or even
how to fix it. Take a look at these articles for instructions on how
to interact meaningfully with the kernel developers:
http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html
http://www.onlamp.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021223121522.GB15678>