From owner-freebsd-questions@FreeBSD.ORG Sun Feb 26 19:24:30 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A03D016A420 for ; Sun, 26 Feb 2006 19:24:30 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 501BE43D45 for ; Sun, 26 Feb 2006 19:24:30 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from topaz-out (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id k1QJOObd015327; Sun, 26 Feb 2006 11:24:25 -0800 From: Kent Stewart To: freebsd-questions@freebsd.org Date: Sun, 26 Feb 2006 11:24:28 -0800 User-Agent: KMail/1.9.1 References: <17409.8562.677322.222883@jerusalem.litteratus.org> <440145EF.5000101@u.washington.edu> <20060226061343.GA4483@xor.obsecurity.org> In-Reply-To: <20060226061343.GA4483@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602261124.28829.kstewart@owt.com> Cc: Garrett Cooper , Kris Kennaway Subject: Re: anyone recognize this panic? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2006 19:24:30 -0000 On Saturday 25 February 2006 22:13, Kris Kennaway wrote: > On Sat, Feb 25, 2006 at 10:08:47PM -0800, Garrett Cooper wrote: > > Kris Kennaway wrote: > > >On Sat, Feb 25, 2006 at 10:33:06PM -0500, Robert Huff wrote: > > >> I just had my -CURRENT* machine crash under moderate load. No > > >>dump is available because the machine locked hard, but I did copy > > >>this off the screen: > > >> > > >>re0: diagnostic failed to receive packet in loopback mode > > >>re0: attach aborted due to hardware diagnostic failure > > >>panic: mtx_lock() of spin mutex (null) @ > > >> /usr/src/sys/netinet/in_pcb,c:862 > > >> > > >> "re0" is a Linksys EG-1032, less than two months old. It was > > >>connected, but had zero traffic at the time of the crash. > > >> Before I take this to current@ - has anyone seen anything like > > >>this before? A quick check of the archives and the web in > > >> general didn't show anything. > > > > > >You need to at least get a traceback from the panic, and > > > preferably a crashdump. > > > > > >Kris > > > > Probably should pass this onto some devs. It seems like a null > > value was passed for locking a mutex in the OS, which is important. > > Having a traceback would be good though... but at least mentioning > > that the issue laid with the re (?) kernel driver would be a start. > > Unfortunately without a traceback the panic string is useless since > it gives you no clue about how the system got into that state. This > kind of panic is often a secondary effect of some other problem. > I can cause this to happen almost at will with a Netgear GA311. It only happens at boot. It will reboot after the panic just fine and, for me, it only happens repeatedly after I do a restart boot from XP. It has never happened if I shut the system down first. I have moved many GBs of distfiles and packages with out causing a panic. I haven't found a way to cause a dmp when it panics. At least, what I have read doesn't work. So, how can I get a dmp, which I can provide a traceback? Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html