From owner-freebsd-smp Tue Nov 3 15:42:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05066 for freebsd-smp-outgoing; Tue, 3 Nov 1998 15:42:22 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from irbs.irbs.com (irbs.irbs.com [209.36.62.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05061 for ; Tue, 3 Nov 1998 15:42:20 -0800 (PST) (envelope-from jc@irbs.com) Received: (from jc@localhost) by irbs.irbs.com (8.8.5/8.8.5) id SAA11399; Tue, 3 Nov 1998 18:36:05 -0500 (EST) Message-ID: <19981103183604.49697@irbs.com> Date: Tue, 3 Nov 1998 18:36:04 -0500 From: John Capo To: freebsd-smp@FreeBSD.ORG Subject: Dog Sloooow SMP Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a Gigabyte 686DLX that has been running an SMP kernel from May 18 just fine. I upgraded to -current and realized that something was wrong when a buildworld was still running the next morning. The second CPU is started and top shows both CPUs being used. I'm building a system from May 18 again to make sure the hardware is OK. Any ideas? John Capo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message