Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Mar 2004 14:10:40 -0500
From:      Don Bowman <don@sandvine.com>
To:        'Kris Kennaway' <kris@obsecurity.org>, Don Bowman <don@sandvine.com>
Cc:        "'current@freebsd.org'" <current@freebsd.org>
Subject:   RE: LOR on current
Message-ID:  <FE045D4D9F7AED4CBFF1B3B813C85337045D86EF@mail.sandvine.com>

next in thread | raw e-mail | index | archive | help
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FE045D4D9F7AED4CBFF1B3B813C85337045D86EF>