From owner-freebsd-smp Fri Jun 27 11:23:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA05697 for smp-outgoing; Fri, 27 Jun 1997 11:23:25 -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 LAA05681 for ; Fri, 27 Jun 1997 11:23:02 -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 MAA02798; Fri, 27 Jun 1997 12:21:08 -0600 (MDT) Message-Id: <199706271821.MAA02798@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Stephen Roome cc: smp@freebsd.org Subject: Re: Weird segfaults etc.. In-reply-to: Your message of "Fri, 27 Jun 1997 18:10:54 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Jun 1997 12:21:08 -0600 Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > I've just upgraded (?) to 3.0-970618-SNAP with SMP, and I'm getting weird > errors this time (last time I supped it down on top of current about 2 > months ago it was rock solid). > > I tend to be getting stuff like, cc1: died with internal signal 10 or 11 > quite often. I saw a similar problem on a standard 2.2.2 machine, but only > once, this happens more regularly while trying to build kernels and the > like. there were minor changes on 5/30, but they are of the nature of "should work or fail". the next major changes were on 6/22, the SMP_PRIVPAGES code. I strongly suggest cvsupping -current (complete world, not just sys) and remaking both kernel and world. --- > Anyway, here's the mptable output, I think mptable might be screwing up, > because I sure as hell put SMP_AUTOSTART in the kernel, and it did it as > well. if you are refering to the lines: # Useful: #options SMP_AUTOSTART # start the additional CPUs you are misunderstanding how the mptable program works. mptable merely reads the MP spec data from the hardware as the BIOS sets it up. It will read the same reguardless of whether a UP or an SMP kernel is currently booted. "option" lines do NOT come from MP spec data, but instead are compiled into the mptable program. they reflect your current choices (as of the time mptable was last modified) for configuring your SMP kernel. the presense or absense of a leading '#' char on a line reflects whether that option would be used in a 'GENERIC' kernel, and is a judgement call in most cases. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD