From owner-freebsd-questions Mon Dec 23 4:15:39 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1323337B401 for ; Mon, 23 Dec 2002 04:15:38 -0800 (PST) Received: from smtp.infracaninophile.co.uk (happy-idiot-talk.infracaninophile.co.uk [81.2.69.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D5AD43EDC for ; Mon, 23 Dec 2002 04:15:36 -0800 (PST) (envelope-from m.seaman@infracaninophile.co.uk) Received: from happy-idiot-talk.infracaninophile.co.uk (localhost.infracaninophile.co.uk [IPv6:::1]) by smtp.infracaninophile.co.uk (8.12.6/8.12.6) with ESMTP id gBNCFR9Y015981 for ; Mon, 23 Dec 2002 12:15:27 GMT (envelope-from matthew@happy-idiot-talk.infracaninophile.co.uk) Received: (from matthew@localhost) by happy-idiot-talk.infracaninophile.co.uk (8.12.6/8.12.6/Submit) id gBNCFMOb015980 for questions@FreeBSD.ORG; Mon, 23 Dec 2002 12:15:22 GMT Date: Mon, 23 Dec 2002 12:15:22 +0000 From: Matthew Seaman To: questions@FreeBSD.ORG Subject: Re: Kernel panic questions.. Message-ID: <20021223121522.GB15678@happy-idiot-talk.infracaninophi> Mail-Followup-To: Matthew Seaman , questions@FreeBSD.ORG References: <200212231101.gBNB1OgQ005929@babelfish.pursued-with.net> <61BD3662-166C-11D7-AA90-003065715DA8@pursued-with.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <61BD3662-166C-11D7-AA90-003065715DA8@pursued-with.net> User-Agent: Mutt/1.5.1i X-Spam-Status: No, hits=-3.3 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02, USER_AGENT,USER_AGENT_MUTT version=2.43 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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