From owner-freebsd-alpha  Thu Jun  7 12:51: 1 2001
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id EDA1237B405
	for <freebsd-alpha@freebsd.org>; Thu,  7 Jun 2001 12:50:58 -0700 (PDT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA23565;
	Thu, 7 Jun 2001 15:50:58 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f57JoSW54677;
	Thu, 7 Jun 2001 15:50:28 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15135.56068.265334.399553@grasshopper.cs.duke.edu>
Date: Thu, 7 Jun 2001 15:50:28 -0400 (EDT)
To: Wilko Bulte <wkb@freebie.demon.nl>
Cc: freebsd-alpha@freebsd.org
Subject: Re: 8 CPU SMP attempt
In-Reply-To: <20010607215149.A1381@freebie.demon.nl>
References: <E157wR8-0007Fc-00@post.mail.nl.demon.net>
	<15135.32057.775489.42931@grasshopper.cs.duke.edu>
	<20010607215149.A1381@freebie.demon.nl>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-alpha.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-alpha>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-alpha>
X-Loop: FreeBSD.org


Wilko Bulte writes:
 > 
 > Possible. I cannot really try as the smallest config would be a single
 > CPU board housing 2 CPUs. Or do we honor the maxcpus (or whatever it
 > is called..) SRM variable?

"whatever its called" works, at least on Matt's 4100, so you could see if a
dual or single processor config boots.  I think its just a bitmask of
available CPUs on most (all?) platforms.

 > > I don't suppose you could map the pc to a file and line number in the
 > > kernel.debug?  (gdb kernel.debug .... (gdb) l *0xfffffc0000491ae4)
 > 
 > I'll have to move the disk back to the dual CPU DS20 on which the same
 > GENERIC booted OK. But that can be done (tnx to the StorageWorks SBB
 > that houses the disk ;)
 > 
 > > A stack trace might be useful too...
 > 
 > I know... But I need to find the time work work this thing between normal
 > work :) Next week we will start moving our complete machine room to another
 > building so that probably also won't help.
 > 

Getting a stack trace shouldn't be all that hard -- just type 'tr'
after it crashes.

Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message