From owner-freebsd-current@FreeBSD.ORG  Fri Jul 16 16:41:18 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 58F7D16A4D0; Fri, 16 Jul 2004 16:41:18 +0000 (GMT)
Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id BB6E343D31; Fri, 16 Jul 2004 16:41:17 +0000 (GMT)
	(envelope-from wjw@withagen.nl)
Received: from dual (dual [212.61.27.71])
	by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i6GGdesD095234;
	Fri, 16 Jul 2004 18:39:41 +0200 (CEST)
	(envelope-from wjw@withagen.nl)
Message-ID: <0b8301c46b52$96931b50$471b3dd4@digiware.nl>
From: "Willem Jan Withagen" <wjw@withagen.nl>
To: "Robert Watson" <rwatson@freebsd.org>
References: <Pine.NEB.3.96L.1040716121933.4361A-100000@fledge.watson.org>
Date: Fri, 16 Jul 2004 18:33:12 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
cc: freebsd-current@freebsd.org
Subject: Re: spin lock sched lock held by 0xffffff007b712250 for > 5 seconds
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2004 16:41:18 -0000

From: "Robert Watson" <rwatson@freebsd.org>
> On Fri, 16 Jul 2004, Willem Jan Withagen wrote:
> 
> > After todays kernelbuild the system seem to be a lot better...
> > It can take quite some buildworld abuse, but still:
> > 
> > spin lock sched lock held by 0xffffff007b712250 for > 5 seconds
> > panic: spin lock held too long
> > cpuid = 1;
> > KDB: enter: panic
> > 
> > But I'm not shure what I could/should do now, since the KDB
> > introduction.  Normally I'd expect to see:  db>
> 
> We have trouble entering the debugger when in a critical section/and or
> have sched_lock held -- I think this is because we try to halt the other
> CPUs and that gets nastily stuck in some form.  We need to fix this.
> 
> This could well be a symptom of some of the other hangs we've been seeing,
> and I've seen similar things on my test box with preemption enabled.

To be honest, it is a lot better than at the beginning of the week.
Anything I can do to help debug either of them??
Suggestions where/what to look for?

--WjW