From owner-freebsd-smp Mon Jun 23 10:50:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA17946 for smp-outgoing; Mon, 23 Jun 1997 10:50:49 -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 KAA17939 for ; Mon, 23 Jun 1997 10:50:46 -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 LAA06493; Mon, 23 Jun 1997 11:50:00 -0600 (MDT) Message-Id: <199706231750.LAA06493@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Lars Fredriksen cc: freebsd-smp@FreeBSD.ORG Subject: Re: Booting SMP on SuperMicro P6DNE fails In-reply-to: Your message of "Sat, 21 Jun 1997 00:01:40 CDT." <199706210501.AAA12670@Mercury.mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jun 1997 11:49:59 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > Building a current kernel (as of last night) with the following > options: > SMP > APIC_IO > SMP_AUTOSTART > SMP_TIMER_NC > > and without I386_CPU and I486_CPU failed to boot. I booted to the point > where you get the TADA message saying that the second processor was > enabled and added to the scheduling queue and the issued a message about > it having found all the cpus. Then it just sat there. I will get a break > into the debugger tomorrow at that point to get a stack backtrace. really need to see the complete printout of the boot. best way to get this is to setup the machine to boot via a serial port, then direct that port thru another machine inside of a tip session under X. you can then cutNpaste the output into a file for examination. having said that this sounds like a missing INTerrupt problem. If I had to guess I would say the disk controller. is it SCSI or IDE? --- > Are there drivers in the 3.0 tree that are not SMP safe? Like the sound > drivers etc?? theoretically they should all be SMP safe, since we use a global "giant lock". but there undoubtedly are a few that do something 'unusual' that could get them in trouble... The general rule in your type problem is to first get a minimal kernel working that has ONLY the drivers you need for booting. then add the others (such as sound, etc.) -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD