From owner-freebsd-current@FreeBSD.ORG Mon Jul 19 15:58:13 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 6914116A4CF for ; Mon, 19 Jul 2004 15:58:13 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4188943D1D for ; Mon, 19 Jul 2004 15:58:13 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 32376 invoked from network); 19 Jul 2004 15:58:13 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Jul 2004 15:58:12 -0000 Received: from 10.50.41.229 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i6JFw7r7012948; Mon, 19 Jul 2004 11:58:08 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org User-Agent: KMail/1.6 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406301130.43121.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Robert Watson 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Mon, 19 Jul 2004 15:58:13 -0000 X-Original-Date: Wed, 30 Jun 2004 11:30:43 -0400 X-List-Received-Date: Mon, 19 Jul 2004 15:58:13 -0000 On Friday 16 July 2004 12:21 pm, Robert Watson wrote: > 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. You can hack sys/i386/include/smptests.h (or smptest.h, whichever it is) and comment out CPUSTOP_ONDDBREAK as a hack. I did that recently for some debugging. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org