From owner-freebsd-questions@FreeBSD.ORG Mon Feb 27 07:52:33 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 5F34F16A420 for ; Mon, 27 Feb 2006 07:52:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12C7243D55 for ; Mon, 27 Feb 2006 07:52:31 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C4D9B1A4E0E; Sun, 26 Feb 2006 23:52:30 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BF44551870; Mon, 27 Feb 2006 02:52:29 -0500 (EST) Date: Mon, 27 Feb 2006 02:52:29 -0500 From: Kris Kennaway To: Kent Stewart Message-ID: <20060227075229.GA16348@xor.obsecurity.org> References: <17409.8562.677322.222883@jerusalem.litteratus.org> <200602261551.44672.kstewart@owt.com> <20060227001804.GA3432@xor.obsecurity.org> <200602262334.12228.kstewart@owt.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline In-Reply-To: <200602262334.12228.kstewart@owt.com> User-Agent: Mutt/1.4.2.1i Cc: Garrett Cooper , freebsd-questions@freebsd.org, 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: Mon, 27 Feb 2006 07:52:33 -0000 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 26, 2006 at 11:34:11PM -0800, Kent Stewart wrote: > It also occurs on RELENG_5 but that machine is my gateway and firewall. >=20 > It may be trying to confuse me but I have to use the NIC in XP before it= =20 > will panic on the FreeBSD boot. My sacrificial machine only runs=20 > 6-stable and it is much harder to make panic. XP is probably leaving the NIC in some kind of inconsistent state, causing the diagnostic error at boot. Fixing that will probably require detailed knowledge of the hardware, but it still should not panic in the error path, and this part should be easier to fix since it's probably just a bad assumption about lock state. Can you submit a PR about this, including the below URLs? > I have 3 280+KB images of the panic and traceback. They are > http://owt-207-41-94-232.owt.com/panic-0.jpg panic > http://owt-207-41-94-232.owt.com/panic-1.jpg 1st page of trace > http://owt-207-41-94-232.owt.com/panic-2.jpg 2nd page of trace Kris --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEAq+9Wry0BWjoQKURAmo5AJ0Ziq3A3huMN2D9nSj59AQfCoI/OgCfQJEf sVUJShoVkSQkVac2mQOyR+g= =M86q -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8--