From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:13:49 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 7331216A4CE for ; Sun, 18 Jul 2004 19:13:49 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31FEB43D49 for ; Sun, 18 Jul 2004 19:13:49 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6IJDKud037781; Sun, 18 Jul 2004 15:13:20 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i6IJDK4S037778; Sun, 18 Jul 2004 15:13:20 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 18 Jul 2004 15:13:20 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Willem Jan Withagen In-Reply-To: <104401c46cf9$480cee40$471b3dd4@digiware.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: panic: Duplicate free of item 0xffffff005c4a8600 from zone 0xffffff007fed4780(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: Sun, 18 Jul 2004 19:13:49 -0000 On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > Starting on: > > > - Try compiling IPv6 out of your kernel -- this will turn on the inpcb > > locking assertions, which are compiled out by default because IPv4 and > > IPv6 share the same underlying pcb code and IPv6 does not yet lock that > > correctly in CVS. I have patches that do quite a bit of that in > > Perforce, and sent out an e-mail yesterday to the KAME folk to talk > > about merging strategies. > > > > - If this is a reproduceable problem, could you try disabling SACK and see > > if it changes at all? > > How do I disable SACK?? Probably there's a flag for, but which.... The sysctl net.inet.tcp.sack.enable enables (and disables) SACK. Given some of the other versions of the trace you're reporting, it's seeming less like it's SACK that's causing the problem, but it's definitely worth trying. We could be looking at an issue with the bge driver -- I have some bge cards and will see about sticking one into a machine here for testing. Can you suggest a workload I can try that will reliably generate the panic for you? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research