From owner-freebsd-smp  Mon Dec  2 21:05:07 1996
Return-Path: owner-smp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA08673
          for smp-outgoing; Mon, 2 Dec 1996 21:05:07 -0800 (PST)
Received: from bluenose.na.tuns.ca (bluenose.na.tuns.ca [134.190.50.156])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA08268
          for <smp@freebsd.org>; Mon, 2 Dec 1996 20:59:38 -0800 (PST)
Received: (from smp@localhost) by bluenose.na.tuns.ca (8.7.6/8.7.3) id AAA12107; Tue, 3 Dec 1996 00:55:18 -0400 (AST)
From: "J.M. Chuang"  <smp@bluenose.na.tuns.ca>
Message-Id: <199612030455.AAA12107@bluenose.na.tuns.ca>
Subject: Re: cvs commit: sys/i386/include spl.h
To: smp@csn.net (Steve Passe)
Date: Tue, 3 Dec 1996 00:55:17 -0400 (AST)
Cc: smp@freebsd.org
In-Reply-To: <199612030449.VAA25502@clem.systemsix.com> from Steve Passe at "Dec 2, 96 09:49:08 pm"
X-Mailer: ELM [version 2.4ME+ PL13 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-smp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> screwy in the "autostart" code.  This is now off by default and the SMP-current
> kernel is stable at this point.  I am very curious to here from one of the EIDE
> testers to see if we fixed that problem also...
> 
I tested. The system can boot without any problem but
if the second cpu is launched, the coredump occurrs to almost
every binary. If I boot the system with the SCSI and fsck IDE, there
are lots of DUP's.... The filesystem is screwed up (I believe).


Jim