From owner-freebsd-smp  Mon Apr 12 17:28:17 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from fire.starkreality.com (fire.starkreality.com [208.24.48.226])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2EE4E153FA; Mon, 12 Apr 1999 17:28:13 -0700 (PDT)
	(envelope-from caesar@starkreality.com)
Received: from grail (grail.starkreality.com [208.24.48.235])
	by fire.starkreality.com (8.9.3/8.9.2) with SMTP id TAA03162;
	Mon, 12 Apr 1999 19:25:52 -0500 (CDT)
Message-Id: <4.1.19990412191627.009b3100@imap.colltech.com>
X-Sender: caesar@mail.starkreality.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Mon, 12 Apr 1999 19:25:31 -0500
To: freebsd-smp@freebsd.org
From: "William S. Duncanson" <caesar@starkreality.com>
Subject: SMP broken in -CURRENT?
Cc: freebsd-current@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I haven't been able to get a working SMP kernel out of -CURRENT recently.
I don't know exactly when it broke, because I usually rebuild on a weekly
basis.  The kernel hangs after:
APIC_IO: Testing 8254 interrupt delivery
and doesn't ever come back (panic or otherwise).

The one thing that I noticed is that on the older kernels, CPU#1 is
launched after the APIC_IO Testing and Routing.  On the newer kernels,
CPU#1 is launched far earlier.

Anybody have any ideas?

On a side note, the pn0 driver appears to be broken (uniprocessor kernels
will boot, the pn0 device shows up, and is ifconfig'd, but there's no link
light on it.  It works fine with older (04/04/99) kernels).


William S. Duncanson                      caesar@starkreality.com
The driving force behind the NC is the belief that the companies who brought us
things like Unix, relational databases, and Windows can make an appliance that
is inexpensive and easy to use if they choose to do that.  -- Scott Adams 


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