From owner-freebsd-smp  Mon Jul  7 09:46:31 1997
Return-Path: <owner-smp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA22703
          for smp-outgoing; Mon, 7 Jul 1997 09:46:31 -0700 (PDT)
Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA22687
          for <freebsd-smp@FreeBSD.ORG>; Mon, 7 Jul 1997 09:46:19 -0700 (PDT)
Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1])
	by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id KAA20706;
	Mon, 7 Jul 1997 10:46:06 -0600 (MDT)
Message-Id: <199707071646.KAA20706@Ilsa.StevesCafe.com>
X-Mailer: exmh version 2.0gamma 1/27/96
From: Steve Passe <smp@csn.net>
To: "Helio Coelho Jr." <helio@compuland.com.br>
cc: freebsd-smp@FreeBSD.ORG
Subject: Re: help in two aspects 
In-reply-to: Your message of "Sun, 06 Jul 1997 10:37:39 -0300."
             <199707061334.KAA25344@sv.compuland.com.br> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 07 Jul 1997 10:46:05 -0600
Sender: owner-smp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

>       I'm running current in a Asus Dual Pentium Pro Motherboard. It has
> 128mb memory, SMC ethernet, adaptec 2940AU and a quantum scsi HD.
> ...
> fine again. Just to be sure, I've repeated the experience, but now, I
> copied
> the disk to the the seagate but removed the big disk and it's 2940UW. I've
> rebooted, and I got the same panic again ! But now with the adaptec2940au
> and the quantum disk ! I turned off and on the machine again: this time it
> came
>  back ! :) Fortunately this time I did not loose the contents of the
> disk...
> Anyone has an idea what happens or were I goofed ? :)

no idea...

---
> Another thing I noticed: when I issue a 'shutdown now' and a 'halt' ,
> sometimes I got
> a 'panic - shutdown not on CPU#0 - automatic reboot in 15 seconds' ... How
> can I avoid
> that ? How can I be sure that I'm on CPU#0 when halting ? ps -x ? :)

does it really say "panic"?  it might say: "oops, I'm on cpu#1, I need to be
on cpu#0!", but thats perfectly normal if you really requested a reboot/halt.
Any 2 successive commands might run on different CPUs, there is no way 
(currently) to guarantee which CPU runs what, but as I said, in this case
its not important.

--
Steve Passe	| powered by 
smp@csn.net	|            Symmetric MultiProcessor FreeBSD