From owner-freebsd-alpha@FreeBSD.ORG Fri Jun 2 16:41:37 2006 Return-Path: X-Original-To: freebsd-alpha@FreeBSD.org Delivered-To: freebsd-alpha@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F93616A42B; Fri, 2 Jun 2006 16:41:37 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr7.xs4all.nl (smtp-vbr7.xs4all.nl [194.109.24.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8549C43D58; Fri, 2 Jun 2006 16:41:34 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr7.xs4all.nl (8.13.6/8.13.6) with ESMTP id k52GfXNl014825; Fri, 2 Jun 2006 18:41:33 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.6/8.13.3) with ESMTP id k52GfXYv008399; Fri, 2 Jun 2006 18:41:33 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.6/8.13.6/Submit) id k52GfWDi008398; Fri, 2 Jun 2006 18:41:32 +0200 (CEST) (envelope-from wb) Date: Fri, 2 Jun 2006 18:41:32 +0200 From: Wilko Bulte To: Robert Watson Message-ID: <20060602164132.GA8376@freebie.xs4all.nl> References: <20060601212736.GA3380@freebie.xs4all.nl> <20060601230007.C69345@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060601230007.C69345@fledge.watson.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@FreeBSD.org, freebsd-alpha@FreeBSD.org Subject: Re: 6.1-RELEASE panic / lockmgr? X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2006 16:41:38 -0000 On Thu, Jun 01, 2006 at 11:01:07PM +0100, Robert Watson wrote.. > > On Thu, 1 Jun 2006, Wilko Bulte wrote: > > >My dual-CPU DS20 Alpha box can more or less consistently be > >forced into a panic like: > > > >FreeBSD/alpha (goldrush.wbnet) (ttyd0)^ > > > >login: panic: lockmgr: thread 0xfffffc007d9d4a80, not exclusive lock holder > >0xfffffc006052d260 unlocking > >cpuid = 1 > >KDB: enter: panic > > > >Trigger is a "make -j2 release". j2 seems to be needed, not seen it with > >-j1 > > > >Unfortunately after printing the line with "KDB" the whole thing appears > >to become completely catatonic :( > > Try putting a call to critical_enter() towards the beginning of panic(). > Sometimes this increases the reliability of entering the debugger by > avoiding interrupt delivery during the process of entering. If you want to > be able to continue out, you'll need a critical_exit() at the end, but that > generally isn't helpful for panic(). Jay! ANother one, and this one entered the debugger alright: racing pid 25497 tid 100147 td 0xfffffc004df56000 kdb_enter() at kdb_enter+0x48 panic() at panic+0x210 lockmgr() at lockmgr+0x798 vop_stdunlock() at vop_stdunlock+0x34 VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x84 vput() at vput+0xb4 lookup() at lookup+0xd38 namei() at namei+0x554 do_execve() at do_execve+0x17c kern_execve() at kern_execve+0x160 execve() at execve+0x60 syscall() at syscall+0x438 XentSys() at XentSys+0x64 --- syscall (59, FreeBSD ELF64, execve) --- --- user mode --- db> How to proceed here? I have 0 clue on lockmgr & friends :) -- Wilko Bulte wilko@FreeBSD.org