From owner-freebsd-stable Thu Mar 6 7:47:56 2003 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 6A11837B401 for ; Thu, 6 Mar 2003 07:47:55 -0800 (PST) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEE1643F85 for ; Thu, 6 Mar 2003 07:47:54 -0800 (PST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.8/8.12.8) with ESMTP id h26Flr57042539; Thu, 6 Mar 2003 10:47:53 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.2.0.9.0.20030306105222.079caf78@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Thu, 06 Mar 2003 10:52:56 -0500 To: "Michael L. Squires" From: Mike Tancsa Subject: Re: Still seeing SMP panics on a older dual PIII (with debug kernel and crash dumps) Cc: FreeBSD Stable In-Reply-To: <200303061545.h26FjtBk003346@siralan.org> References: <5.2.0.9.0.20030306071303.081fe368@192.168.0.12> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: By Sentex Communications (lava/20020517) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:45 AM 06/03/2003 -0500, Michael L. Squires wrote: > > Its an older dual PIII. Can anyone tell me if the dumps point to a > > hardware issue, or if its crashing in the same spot each time ? I can > blast > > it with buildworlds and it never dies. Generally I have yet to find bad > > hardware that could pass that.... But always a first time. > >I have a P6DGH with two PII/300's running 4.8-RC2; mptable crashes with >a "HOSED" error message for the extended table (indicative of a BIOS >problems) but no crashes. A BIOS problem ? In what way ? ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message