From owner-freebsd-current@FreeBSD.ORG Fri Jul 16 17:38:41 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 3201F16A4CE; Fri, 16 Jul 2004 17:38:41 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2415343D48; Fri, 16 Jul 2004 17:38:40 +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 i6GHaxsD096418; Fri, 16 Jul 2004 19:36:59 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <0bec01c46b5a$98469e10$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Willem Jan Withagen" , "Robert Watson" References: <0b8301c46b52$96931b50$471b3dd4@digiware.nl> Date: Fri, 16 Jul 2004 19:30:31 +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: One more ..... 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: Fri, 16 Jul 2004 17:38:41 -0000 From: "Willem Jan Withagen" To: "Robert Watson" Cc: Sent: Friday, July 16, 2004 6:33 PM Subject: Re: spin lock sched lock held by 0xffffff007b712250 for > 5 seconds > From: "Robert Watson" > > 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? panic: process 82471(sh):2 holds Giant but isn't blocked on a lock cpuid = 1; KDB: enter: panic Is there any purpose in reporting these crashes this way??? --WjW