From owner-freebsd-stable@FreeBSD.ORG Thu Feb 18 21:24:30 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DEF91065676 for ; Thu, 18 Feb 2010 21:24:30 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [194.58.105.35]) by mx1.freebsd.org (Postfix) with ESMTP id 0057D8FC0A for ; Thu, 18 Feb 2010 21:24:29 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NiDrI-0007nK-N2; Fri, 19 Feb 2010 00:24:28 +0300 Date: Fri, 19 Feb 2010 00:24:28 +0300 From: Slawa Olhovchenkov To: Pyun YongHyeon Message-ID: <20100218212428.GJ55307@zxy.spb.ru> References: <147432021002141004o6c1412b7gd548b87709532ef9@mail.gmail.com> <20100216175719.GB1394@michelle.cdnetworks.com> <20100218143822.GA8380@zxy.spb.ru> <20100218193612.GB11675@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100218193612.GB11675@michelle.cdnetworks.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Nick Rogers , stable@freebsd.org Subject: Re: trap 12: page fault while in kernel mode on 8.0-RELEASE (possibly bge(4) related) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2010 21:24:30 -0000 On Thu, Feb 18, 2010 at 11:36:12AM -0800, Pyun YongHyeon wrote: > On Thu, Feb 18, 2010 at 05:38:22PM +0300, Slawa Olhovchenkov wrote: > > On Tue, Feb 16, 2010 at 09:57:19AM -0800, Pyun YongHyeon wrote: > > > > > On Sun, Feb 14, 2010 at 10:04:58AM -0800, Nick Rogers wrote: > > > > I'm having repeated kernel panic issues on 8.0-RELEASE/amd64. Can anyone > > > > shed light on the below error? I unfortunately cannot provide a proper crash > > > > dump. The pointer addresses are always the same. The only other thing I've > > > > noticed that may be related is a watchdog timeout on bge0 error before the > > > > panic. Thanks. > > > > > > > > > > Any chance to get backtrace from the crash? > > > > I got same trouble on the same platform (8.0-STABLE/amd64). > > hw.bge.allow_asf=0 already > > > > I got 2 proper crash dump (first w/ net.inet.ip.forwarding=1 > > and second w/ net.inet.ip.forwarding=0). > > > > It looks like mbuf pointer was changed to NULL in the middle of IP > forwarding and IP fragment stage. If bge(4) frees passed mbufs this > may happen but I'm not sure this comes from bge(4). > By chance, are you using polling(4) on bge(4)? Also show me the I am not using polling. > dmesg output(only bge(4) related one). dmesg from boot: bge0: mem 0xfdf70000-0xfdf7ffff irq 25 at device 2.0 on pci2 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:14:c2:3d:e5:52 bge0: [ITHREAD] bge1: mem 0xfdf60000-0xfdf6ffff irq 26 at device 2.1 on pci2 miibus1: on bge1 brgphy1: PHY 1 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge1: Ethernet address: 00:14:c2:3d:e5:51 bge1: [ITHREAD] bge1: link state changed to UP bge0: link state changed to UP Nothing in dmesg before trap. -- Slawa Olhovchenkov