From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 23:06:47 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 48DFF16A4CE; Sun, 18 Jul 2004 23:06:47 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24D2843D3F; Sun, 18 Jul 2004 23:06:46 +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 i6IN4wsD062878; Mon, 19 Jul 2004 01:04:59 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <115601c46d1a$bf9f4540$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Robert Watson" References: Date: Mon, 19 Jul 2004 00:58:32 +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 zone0xffffff007fed4780(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 23:06:47 -0000 From: "Robert Watson" > On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > > > > Three stikes and out.... > > > I'll disable mpsafe now.... > > > > Does not seem to help.... Not shure if anything should be read in the > > fact that it is 3 times in [thread 100007]. > > 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. Just as I was writing: ================ I would dare to declare the current running config stable, but it is up for more than 2,5 hours. While taking the abuse that normaly would bring the system on its knees within 30 minutes... I'm now running: bge0 interface No IPv6 debug.mpsafe=0 Which would lead me to believe problems in the IPv6 layer (with bge0?). ================ It got negated by: panic: lock (sleep mutex) UMA pcpu not locked @ /home2 /src/sys/vm/uma_core.c:1654 cpuid = 1; KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x34 panic() at panic+0x1d2 witness_unlock() at witness_unlock+0xdd _mtx_unlock_flags() at _mtx_unlock_flags+0x68 uma_zalloc_arg() at uma_zalloc_arg+0x14e tcp_output() at tcp_output+0xce9 tcp_input() at tcp_input+0x27f5 ip_input() at ip_input+0x94c netisr_processqueue() at netisr_processqueue+0x8c swi_net() at swi_net+0xaf ithread_loop() at ithread_loop+0x18d fork_exit() at fork_exit+0xc9 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffb0bb9d00, rbp = 0 --- KDB: enter: panic [thread 100017] Stopped at kdb_enter+0x2e: nop I'll starts some more tests before I'm of to bed. --WjW