From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 12:23:40 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 93BF716A4CE for ; Wed, 24 Mar 2004 12:23:40 -0800 (PST) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41C0443D55 for ; Wed, 24 Mar 2004 12:23:40 -0800 (PST) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Wed, 24 Mar 2004 15:23:37 -0500 Message-ID: From: Don Bowman To: 'Kris Kennaway' , Don Bowman Date: Wed, 24 Mar 2004 15:23:36 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: "'current@freebsd.org'" 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 20:23:40 -0000 From: Kris Kennaway [mailto:kris@obsecurity.org] > 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 > > > > > serial before locking up: > > > > > > > > And I got another, but this one it recovered from after a ~20s > > > > hang. > > > > > > > > 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. > > > > > > You really need to do some research before submitting the > 500th copy > > > of 2 non-bug reports :-) > > > > 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. > > > > is it expected that one can get a core or panic or into db > > at this time? > > > > 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 :) Not being one to believe in coincidences... I'm typing on the serial console. The machine halts, i can no longer type. some seconds pass, out pops that message. This time too it returned. Most times (when i run two postgresql vacuums simulatenously for example), that's the end of it. I will continue to investigate.