From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 19:47:15 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 BBC4F16A4CE; Sun, 18 Jul 2004 19:47:15 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23B5943D1D; Sun, 18 Jul 2004 19:47:15 +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 i6IJjSsD059041; Sun, 18 Jul 2004 21:45:29 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <108901c46cfe$e02ec130$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: Date: Sun, 18 Jul 2004 21:39:00 +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 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:47:15 -0000 From: "Robert Watson" > On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > > > > Well, the threads involved seem to be the netisr thread and the bge > > > interrupt thread, suggesting we have a problem with mbufs being free'd > > > despite being handed off into the network stack. Up front, it suggests > > > maybe we have an issue with the bge driver freeing or reusing an mbuf > > > inappropriately, or perhaps it's at the TCP layer. > > > > Even more reason to do some (ab)using test with the em0 card??? > > Yeah, that would be very helpful if you could. Well uptill now it was less than 30 minutes to get a crash.... No counting the ones where it directly crashed whilest booting. So we could get to > 20 crashes/sunday :) I now got a kernel with no IPv6. First abuse that with bge0. But if it is what you think it is, it'll make no difference. Note that I can get annottated traces with param-values and line numbers if I coredump the panics. But dumping core and saving it, takes almost just as long as causing one. --WjW