From owner-freebsd-current@FreeBSD.ORG Tue Apr 15 13:07:11 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98F0837B405 for ; Tue, 15 Apr 2003 13:07:11 -0700 (PDT) Received: from mail.speakeasy.net (mail13.speakeasy.net [216.254.0.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA65D43FA3 for ; Tue, 15 Apr 2003 13:07:10 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 7212 invoked from network); 15 Apr 2003 20:07:17 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 15 Apr 2003 20:07:17 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h3FK77Ov070125; Tue, 15 Apr 2003 16:07:07 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20030415185118.GA65629@rot13.obsecurity.org> Date: Tue, 15 Apr 2003 16:07:09 -0400 (EDT) From: John Baldwin To: Kris Kennaway cc: current@FreeBSD.ORG Subject: Re: Another "impossible" mutex panic (Re: Panic in wait4()) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2003 20:07:12 -0000 On 15-Apr-2003 Kris Kennaway wrote: > On Tue, Apr 15, 2003 at 10:29:29AM -0700, Kris Kennaway wrote: >> On Tue, Mar 25, 2003 at 02:22:04PM -0800, Kris Kennaway wrote: >> > I just got this on bento (running a kernel from Mar 17). It was under >> > heavy disk load at the time, which may or may not be relevant. >> > >> > Kris >> > >> > panic: mtx_lock() of spin mutex %s @ %s:%d >> > panic messages: >> >> I just got another one of these "impossible" panics on one of the >> gohans (impossible because according to gdb the mutex is not a spin >> mutex, so the assertion should not have fired). > > I got this a third and fourth time on another two gohans (same > backtrace). Best guess is that someone is doing a lock on a mutex that has been destroyed. Possibly the memory has been overwritten by something else. What does gdb show for the contents of the actual mutex? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/