From owner-freebsd-smp Fri Jul 18 21:43:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06255 for smp-outgoing; Fri, 18 Jul 1997 21:43:50 -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 VAA06250 for ; Fri, 18 Jul 1997 21:43:46 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.6/8.8.5) with ESMTP id WAA20958 for ; Fri, 18 Jul 1997 22:43:14 -0600 (MDT) Message-Id: <199707190443.WAA20958@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: smp@freebsd.org Subject: HEADS UP: major timer/APIC code changes. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Jul 1997 22:43:14 -0600 Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I have done major hacking to the APIC code in the areas of the 8254 timer and RTC timer. Some of these involve the EISA changes discussed earlier. Others are an attempt to bury the SMP_TIMER_NC code. The latest code will fail to build with "options SMP_TIMER_NC" set in your config file, remove & reconfig to build a new kernel. Its working well on my dual P6 which needs the timer redirect code, but paniced my dual P5 which doesn't. The panic was in modload, removing the "star" screensaver from sysconfig allowed it to boot, so I am assumming its unrelated. I am in the middle of a cvsup of the world for that machine and will report after a make world. Please send me reports for ANY new kernel builds, working or not. I need to know ASAP whether I've broken anything. This is one of those changes that may behave differently on various hardware. The affected code is identifiable by sys/i386/include/smptests.h: * $Id: smptests.h,v 1.13 1997/07/19 03:56:30 fsmp Exp $ -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD