From owner-freebsd-questions@FreeBSD.ORG Sun Feb 26 06:08:49 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 7854C16A420 for ; Sun, 26 Feb 2006 06:08:49 +0000 (GMT) (envelope-from youshi10@u.washington.edu) Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 198EC43D45 for ; Sun, 26 Feb 2006 06:08:49 +0000 (GMT) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1Q68m1d018086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 25 Feb 2006 22:08:48 -0800 X-Auth-Received: from [128.208.4.242] (nilakantha.cs.washington.edu [128.208.4.242]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1Q68mak002770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sat, 25 Feb 2006 22:08:48 -0800 Message-ID: <440145EF.5000101@u.washington.edu> Date: Sat, 25 Feb 2006 22:08:47 -0800 From: Garrett Cooper User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <17409.8562.677322.222883@jerusalem.litteratus.org> <20060226033858.GA10985@xor.obsecurity.org> In-Reply-To: <20060226033858.GA10985@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' 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 06:08:49 -0000 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. -Garrett