From owner-freebsd-current@FreeBSD.ORG Tue Nov 9 13:40:55 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 B502A16A4CE for ; Tue, 9 Nov 2004 13:40:55 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F3F543D49 for ; Tue, 9 Nov 2004 13:40:55 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iA9Ddl6L052314; Tue, 9 Nov 2004 08:39:47 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iA9Ddl15052311; Tue, 9 Nov 2004 13:39:47 GMT (envelope-from robert@fledge.watson.org) Date: Tue, 9 Nov 2004 13:39:47 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Vincent Poy In-Reply-To: <429af92e0411082025680d70e3@mail.gmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@FreeBSD.ORG Subject: Re: latest -CURRENT kernel panic 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, 09 Nov 2004 13:40:55 -0000 On Mon, 8 Nov 2004, Vincent Poy wrote: > I updated from a March 6, 2004 -CURRENT which had been running without > issues to October 19, 2004 -CURRENT. All -CURRENT since October 19, > 2004 to the latest November 5, 2004 -CURRENT have been panicing with the > following: Looks like it's likely a bug in the if_xl device driver. Looks like Garance has already pointed you at the debugging guide in the handbook, in particular using a serial console via a second box to avoid having to type. In addition to that useful stuff, it would be useful to have you try the following: - if debug.mpsafenet=1, please try temporarily setting debug.mpsafenet=0 in loader.conf and rebooting to see if the problem goes away. This might suggest a locking problem in the xl driver, for example. - Could you use gdb or addr2line to convert xl_intr+0x262 below into a source line number? - Could you run "show pcpu", "show locks", and "ps" and provide that output (serial console highly recommended). - Could you tell me what sort of load the system is experiencing -- in particular, does it have multiple network interfaces, is it performing web serving, packet forwarding, bridging, XWindows, etc? - Are you running with any tweaked network settings, such as net.isr.enable? Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > Slab at 0xc3d75fa8, freei 14 = 0. > panic: Duplicate free of item 0xc3d75e00 from zone 0xc143e9a0(Mbuf) > cpuid = 0 > KDB: enter: panic > [thread 100019] > Stopped at kdb_enter+0x2c: leave > db> trace > kdb_enter(c0852d05,100,c38b0980,e,c3d75000) at kdb_enter+0x2c > panic(c086ce77,c3d75e00,c143e9a0,c08515e0,c086ce5b) at panic+0x17f > uma_dbg_free(c143e9a0,0,c3d75e00) at uma_dbg_free+0x10e > uma_zfree_arg(c143e9a0,c3d75e00,0) at uma_zfree_arg+0x1f6 > m_freem(c3d75e00,c3a0b21c,c3a0b2f4,c3a0cd80,c38b7400) at m_freem+0x3e > xl_intr(c3a09000,0,c38b3c00,0,c0612120) at xl_intr+0x262 > ithread_loop(c38b7400,e9f95d48,c38b7400,c0612120,0) at ithread_loop+0x186 > fork_exit(c0612120,c38b7400,e9f95d48) at fork_exit+0x7e > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xe9f95d7c, ebp = 0 --- > db> > > Any ideas what could be causing this? Is there anyway to write > everything above to a file instead of manually typing everything? > Thanks. > > Cheers, > Vince > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >