From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 07:07:09 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 0A87416A4CE; Tue, 20 Jul 2004 07:07:09 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10B8443D5F; Tue, 20 Jul 2004 07:07:08 +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 i6K75EsD000848; Tue, 20 Jul 2004 09:05:15 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <15fd01c46e27$02e49050$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: Date: Tue, 20 Jul 2004 08:58:49 +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: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 fromzone0xffffff007fed4780(Mbuf) 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: Tue, 20 Jul 2004 07:07:09 -0000 From: "Robert Watson" > On Mon, 19 Jul 2004, Willem Jan Withagen wrote: > > > > I'll starts some more tests before I'm of to bed. > > > > This mornings result: > > ==== > > System call getdirentries returning with the following locks held: > > exclusive sleep mutex bdone lock r = 0 (0xffffffff805fd080) locked @ /home2/src/ > > sys/kern/vfs_bio.c:3767 > > panic: witness_warn > > cpuid = 0; > > KDB: stack backtrace: > > kdspin lock sched lock held by 0xffffff007b6cc940 for > 5 seconds > > panic: spin lock held too long > > cpuid = 0; > > KDB: enter: panic > > ==== > > > > But no way to get into the debugger. Does not look like it is much > > network related??? > > Doesn't look very network related, although it could be that increased > concurrency and lack of waiting on Giant open up a race of some sort. Can > you confirm "options DDB" and "options KDB" are both in your kernel > config? You may want to consider commenting out "#define PREEMPTION" in > the copy of params.h for the architecture you're running on and see if > that helps. Won't help interrupt processing latency, but probably won't > hurt server throughput, and your box is a server box so it might be worth > trying. The first time that it made it through the night since quite some days... The real stress test, "make -j32 buildworld" is still too much however. --WjW