From owner-freebsd-alpha@FreeBSD.ORG Fri Jun 2 01:06:01 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 C328416AA4F; Fri, 2 Jun 2006 01:06:01 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D6E443D45; Fri, 2 Jun 2006 01:06:01 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 671461A4E8E; Thu, 1 Jun 2006 18:06:01 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D293E5153E; Thu, 1 Jun 2006 21:06:00 -0400 (EDT) Date: Thu, 1 Jun 2006 21:06:00 -0400 From: Kris Kennaway To: Robert Watson Message-ID: <20060602010600.GB40143@xor.obsecurity.org> References: <20060601212736.GA3380@freebie.xs4all.nl> <20060601230007.C69345@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1LKvkjL3sHcu1TtY" Content-Disposition: inline In-Reply-To: <20060601230007.C69345@fledge.watson.org> User-Agent: Mutt/1.4.2.1i 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 01:06:01 -0000 --1LKvkjL3sHcu1TtY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 01, 2006 at 11:01:07PM +0100, Robert Watson wrote: >=20 > On Thu, 1 Jun 2006, Wilko Bulte wrote: >=20 > >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 hol= der > >0xfffffc006052d260 unlocking > >cpuid =3D 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= =20 > >to become completely catatonic :( >=20 > Try putting a call to critical_enter() towards the beginning of panic().= =20 > Sometimes this increases the reliability of entering the debugger by=20 > avoiding interrupt delivery during the process of entering. If you want = to=20 > be able to continue out, you'll need a critical_exit() at the end, but th= at=20 > generally isn't helpful for panic(). Also turn off debug.kdb.stop_other_cpus or whatever it is. Without this I usually get lockups on sparc64 SMP machines. Kris --1LKvkjL3sHcu1TtY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEf474Wry0BWjoQKURAlraAJ93l1zRM8ns++7JiTLEMKriDpLhOgCeL4qE F02s26wlPiSNn+SMxdIlpNo= =D903 -----END PGP SIGNATURE----- --1LKvkjL3sHcu1TtY--