From owner-freebsd-current  Fri Nov 17  3:57:15 2000
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 3832337B479
	for <current@FreeBSD.ORG>; Fri, 17 Nov 2000 03:57:12 -0800 (PST)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id MAA92493;
	Fri, 17 Nov 2000 12:55:28 +0100 (CET)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200011171155.MAA92493@freebsd.dk>
Subject: Re: CURRENT is freezing again ...
In-Reply-To: <2967.974461715@axl.fw.uunet.co.za> from Sheldon Hearn at "Nov 17, 2000 01:48:35 pm"
To: sheldonh@uunet.co.za (Sheldon Hearn)
Date: Fri, 17 Nov 2000 12:55:28 +0100 (CET)
Cc: bright@wintelcom.net (Alfred Perlstein),
	steve@virtual-voodoo.com (Steven E. Ames), bp@butya.kz (Boris Popov),
	valentin@valcho.net (Valentin Chopov), current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Sheldon Hearn wrote:
> > I would try a new kernel, and perhaps some collabaration with John
> > to debug these problems rather than just complaining about the
> > situation.  I see at least two experianced developers in the CC
> > list, there's no reason for these poor bug reports.
> 
> The problem with a hard lock-up out of which you can't escape into the
> debugger is that it makes meaningful bug reports impossible.  My non-SMP
> workstation has exhibited apparently arbitrary lock-ups since the advent
> of SMPng.
> 
> I thought I was the only one, since my question on the freebsd-current
> mailing list went unanswered.

You are _not_ alone, there has been numerous complains about this
on the list, but so far they have not been taken seriously :|

> >From my understanding, John's WITNESS code allows us to break into the
> debugger from within interrupt context.  If the lock-ups are happening
> in there, then this may help us provide better bug reports.

It doesn't help here at least, the machine(s) just lock up solid
only reset or a powercycle can bring them back...

> Oh, and a couple of deep breaths are probably in order. :-)

Yeah like *sigh* ....

-Søren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message