From owner-freebsd-stable@FreeBSD.ORG Thu Oct 12 09:37:40 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1855316A4CA for ; Thu, 12 Oct 2006 09:37:40 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9CD943D6A for ; Thu, 12 Oct 2006 09:37:30 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k9C9bGp2096870 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Oct 2006 13:37:16 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k9C9bEih096868; Thu, 12 Oct 2006 13:37:14 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 12 Oct 2006 13:37:14 +0400 From: Gleb Smirnoff To: Kevin Kramer Message-ID: <20061012093714.GL59833@FreeBSD.org> References: <20061011093139.df4b6fbf.wmoran@collaborativefusion.com> <452D0986.3020902@samsco.org> <452D1A07.4070500@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <452D1A07.4070500@centtech.com> User-Agent: Mutt/1.5.6i Cc: davidch@broadcom.com, Bill Moran , stable@FreeBSD.org, netops@collaborativefusion.com, kris@obsecurity.org Subject: Re: bce issues still outstanding 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, 12 Oct 2006 09:37:40 -0000 Kevin, On Wed, Oct 11, 2006 at 11:21:27AM -0500, Kevin Kramer wrote: K> here is a picture of a panic i get on a Dell Precision 390 booting K> 6.2-beta2_amd64. hope this helps. K> K> http://users.centtech.com/~kramer/broadcom/bge_prec390.jpg Well, although the message above is about bge(4) identified, the panic says that the CPU received NMI due to RAM parity error. Have you tried replacing the RAM? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE