From owner-freebsd-smp Tue Feb 24 11:27:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20683 for freebsd-smp-outgoing; Tue, 24 Feb 1998 11:27:01 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20663; Tue, 24 Feb 1998 11:26:40 -0800 (PST) (envelope-from smp@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id MAA00440; Tue, 24 Feb 1998 12:26:29 -0700 (MST) Message-Id: <199802241926.MAA00440@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: sos@FreeBSD.ORG cc: smp@FreeBSD.ORG Subject: Re: mpfps Base Table HOSED! In-reply-to: Your message of "Tue, 24 Feb 1998 20:08:13 +0100." <199802241908.UAA00375@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 24 Feb 1998 12:26:29 -0700 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA20671 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > In reply to Steve Passe who wrote: > > Hi, > > > > > > I've just updated the BIOS on my TYAN 1662D board to 4.0E with > > > NCR SCSI extensions, and this is what I'm told: > > > > > > PANIC: mpfps Base Table HOSED! > > > > > > This is because there is some new entries in the tabel with type # 176 > > > and the system doesn't understand those (mp_machdep.c). > > > I've temporarily disabled the panic for those values and the system > > > runs without problems... > > > Any ideas of what those values mean ?? > > > Should we let them pass without panic'ing ?? > > > > I just searched the Intel site, nothing newer than MPspec 1.4 there. > > Page 4-6 of the 1-4 spec lists the legal types, and says "All other type > > codes are reserved". So if we want to be correct this should probably > > be handled as a "rogue hardware" situation till we have reason to believe > > otherwise. > > Well, I've put in a case for 176 to just ignore that value, the system > is rock stable still, so its not of much importance... > Is there any precedence on how we handle these, by config option ?? Traditionally I've used config options, perhaps 'IGNORE_MPTABLE_176' would be good. Then document it in LINT in the SMP section. At the very least I would want an informational message to come out to the console about "ignoring invalid MPtable entry: #xx: during boot if this goes into the tree. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message