From owner-freebsd-current  Mon Aug 11 20:24:40 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id UAA22793
          for current-outgoing; Mon, 11 Aug 1997 20:24:40 -0700 (PDT)
Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA22768
          for <current@FreeBSD.ORG>; Mon, 11 Aug 1997 20:24:33 -0700 (PDT)
Received: (from uucp@localhost)
	by abby.skypoint.net (8.8.5/alexis 2.7)  with UUCP id WAA01000; Mon, 11 Aug 1997 22:18:23 -0500 (CDT)
Received: (from bruce@localhost)
	by zuhause.mn.org (8.8.7/8.8.5) id WAA00320;
	Mon, 11 Aug 1997 22:10:52 -0500 (CDT)
Date: Mon, 11 Aug 1997 22:10:52 -0500 (CDT)
Message-Id: <199708120310.WAA00320@zuhause.mn.org>
From: Bruce Albrecht <bruce@zuhause.mn.org>
To: Steve Passe <smp@csn.net>
Cc: current@FreeBSD.ORG
Subject: Re: Trap 9 When Boot SMP 
In-Reply-To: <199708111657.KAA15898@Ilsa.StevesCafe.com>
References: <199708110633.BAA00276@zuhause.mn.org>
	<199708111657.KAA15898@Ilsa.StevesCafe.com>
X-Mailer: VM 6.30 under 19.15p2 XEmacs Lucid
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Steve Passe writes:
 > do you recall what those hardware changes were?

I had a disk drive die, so I replaced it, and I also reseated all of
the SIMMs and PCI cards.  Since then, I've also had the motherboard
replaced because one of the CPU fan flanges broke during shipping.

 > I don't see the Matrox being trouble at boot as there is no code specific
 > to that card at boot time.  The NCR code is a possibility,  what/who's BIOS
 > are you using for the NCR card?

It's an AMI Tyan Titan-Pro V3.00  10/25/96 BIOS, but this also failed
with the Award BIOS.  The NCR card uses the Symbios Logic SDMS
V4.0 PCI SCSI BIOS, PCI Rev 2.0, 2.1 PCI-4.03.02.

 > 
 > I'll add this patch to the code as some sort of "#ifdef 0" thing and document
 > it as rogue hardware.  Not much else to do until we can nail down exactly
 > what the prblem is caused by.

I don't have the time to do anything to help track this down for the
next week or so, but I'll touch base then to see what I might do to
help then.