From owner-freebsd-stable@FreeBSD.ORG Mon Nov 2 16:45:45 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7028106566B for ; Mon, 2 Nov 2009 16:45:45 +0000 (UTC) (envelope-from npapke@acm.org) Received: from idcmail-mo1so.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id 915D68FC0A for ; Mon, 2 Nov 2009 16:45:45 +0000 (UTC) Received: from pd2ml1so-ssvc.prod.shaw.ca ([10.0.141.139]) by pd4mo1so-svcs.prod.shaw.ca with ESMTP; 02 Nov 2009 09:45:44 -0700 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.0 c=1 a=68cLX4VTzOUA:10 a=VF9RaR9bft6c8SsOr3WyFg==:17 a=N54-gffFAAAA:8 a=lvbMJxvVAAAA:8 a=-jUdDOQdOwDuEVuOtqMA:9 a=5Nn3DeFWu35x8-e6WAdo5oV2okcA:4 a=nAPXUAfsBmEA:10 Received: from unknown (HELO proven.lan) ([24.85.241.34]) by pd2ml1so-dmz.prod.shaw.ca with ESMTP; 02 Nov 2009 09:45:44 -0700 Received: from proven.lan (localhost [127.0.0.1]) by proven.lan (8.14.3/8.14.3) with ESMTP id nA2Gjixv003062; Mon, 2 Nov 2009 08:45:44 -0800 (PST) (envelope-from npapke@acm.org) Received: from localhost (localhost [[UNIX: localhost]]) by proven.lan (8.14.3/8.14.3/Submit) id nA2GjinE003061; Mon, 2 Nov 2009 08:45:44 -0800 (PST) (envelope-from npapke@acm.org) X-Authentication-Warning: proven.lan: npapke set sender to npapke@acm.org using -f From: Norbert Papke Organization: Archaeological Filing To: pyunyh@gmail.com Date: Mon, 2 Nov 2009 08:30:43 -0800 User-Agent: KMail/1.9.10 References: <200910292156.19845.npapke@acm.org> <200910301823.51274.npapke@acm.org> <20091031212107.GC17243@michelle.cdnetworks.com> In-Reply-To: <20091031212107.GC17243@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200911020830.44343.npapke@acm.org> Cc: freebsd-stable@freebsd.org Subject: Re: 7.2 Stable Crash - possibly related to if_re 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: Mon, 02 Nov 2009 16:45:46 -0000 On October 31, 2009, Pyun YongHyeon wrote: > On Fri, Oct 30, 2009 at 06:23:51PM -0700, Norbert Papke wrote: > > On October 30, 2009, Pyun YongHyeon wrote: > > > On Thu, Oct 29, 2009 at 09:56:19PM -0700, Norbert Papke wrote: > > > > This occurred shortly after "scp"ing from a VirtualBox VM to the > > > > host. The file transfer got stuck. The "re" interface stopped > > > > working. Shortly afterwards, the host crashed. The "re" interface > > > > was used by the host, the guest was using a different NIC in bridged > > > > mode. > > > > > > > > > > > > FreeBSD proven.lan 7.2-STABLE FreeBSD 7.2-STABLE #5 r198666: Thu Oct > > > > 29 18:36:57 PDT 2009 > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > cpuid = 0; apic id = 00 > > > > fault virtual address = 0x18 > > > > > > It looks like a NULL pointer dereference, possibly mbuf related > > > one. > > > > > > > fault code = supervisor write data, page not present > > > > instruction pointer = 0x8:0xffffffff80d476ee > > > > stack pointer = 0x10:0xffffff8000078ae0 > > > > frame pointer = 0x10:0xffffff8000078b40 > > > > code segment = base 0x0, limit 0xfffff, type 0x1b > > > > = DPL 0, pres 1, long 1, def32 0, gran 1 > > > > processor eflags = interrupt enabled, resume, IOPL = 0 > > > > current process = 18 (swi5: +) > > > > Physical memory: 8177 MB > > > > > > > By chance, did you stop the re0 interface with ifconfig when you > > > noticed the file transfer got stuck? > > > > It is possible. I had it happen twice. The first time I definitely > > tried to "down" re. I cannot recall what I did the second time. The > > crash dump is from the second time. > > Ok, then would you try attached patch? I have been running with patch for a couple of days now. Although I can still reproduce the problem with the file transfer, I have not been able to reproduce the panic. The patch appears to do what it is supposed to do. I am going to continue to try to come up with a better test case for the original file transfer problem. I no longer suspect "re" as a cause. Thank you very much for your help. Cheers, -- Norbert Papke. npapke@acm.org http://saveournet.ca Protecting your Internet's level playing field