From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 11:38:28 2004 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 DEE0116A4CE for ; Wed, 24 Mar 2004 11:38:28 -0800 (PST) Received: from mta7.pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id B98F843D4C for ; Wed, 24 Mar 2004 11:38:28 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (469e13727fff81a670b464fe0b1a4d17@adsl-67-119-53-203.dsl.lsan03.pacbell.net [67.119.53.203])i2OJcSsu019173; Wed, 24 Mar 2004 11:38:28 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AF31C5283A; Wed, 24 Mar 2004 11:38:27 -0800 (PST) Date: Wed, 24 Mar 2004 11:38:27 -0800 From: Kris Kennaway To: Don Bowman Message-ID: <20040324193827.GA53252@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: "'current@freebsd.org'" cc: 'Kris Kennaway' Subject: Re: LOR on current 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: Wed, 24 Mar 2004 19:38:29 -0000 --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 24, 2004 at 02:10:40PM -0500, Don Bowman wrote: > From: Kris Kennaway [mailto:kris@obsecurity.org] > > On Wed, Mar 24, 2004 at 11:04:03AM -0500, Don Bowman wrote: > > > From: Don Bowman [mailto:don@sandvine.com] > > > > So my machine which has been locking up daily under current > > > > (cvs up from saturday) this time showed this message to=20 > > > > serial before locking up: > > >=20 > > > And I got another, but this one it recovered from after a ~20s > > > hang. > > >=20 > > > machine has 4GB ram, adaptec ASR raid, 2 2.8GHz xeon with > > > symmetric multi threading yielding 4 processor contexts. > > > The only process it runs (other than system related stuff) > > > is postgresql. > >=20 > > You really need to do some research before submitting the 500th copy > > of 2 non-bug reports :-) >=20 > I was hoping that it would jog someone's memory. I've been > trying to do some research, but have not found a patch to > the problem. The machine locks up entirely, no debugger or anything, > so i'm at a bit of a loss not having debugged these before. >=20 > is it expected that one can get a core or panic or into db > at this time? >=20 > As you can imagine, searching for lock order reversal returns > a lot of hits. > is it 'kern/60581: lock order reversal'? this indicates its > a 'known false positive'... But my machine locks up solid. > So i think that's not it. Right, I think that's not the cause of your lockup :) Kris --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAYeOzWry0BWjoQKURArCPAJ0ds+Fvztagf6tg6kkfRbN3SCHdDgCg6nPv mLAqdmCGjZgcBlJobs0oxjA= =vJWy -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--