From owner-freebsd-stable Wed Jan 10 12: 4:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id F1B6437B404 for ; Wed, 10 Jan 2001 12:04:28 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0AK38Y14826; Wed, 10 Jan 2001 12:03:08 -0800 (PST) Date: Wed, 10 Jan 2001 12:03:07 -0800 From: Alfred Perlstein To: "O. Hartmann" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: massive SMP problems ... Message-ID: <20010110120307.G7240@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ohartman@ipamzlx.physik.uni-mainz.de on Wed, Jan 10, 2001 at 08:07:23PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No mention of what version of FreeBSD you're actually running makes it hard to diagnose except for: * O. Hartmann [010110 11:04] wrote: > the first cvsupdate and today the same. The end of the story is, that > our server is very instable. Sometimes I get obscure errors about not > working gcc, cpp ends up with a fatal error 11. The changes in the kernel Looks like you have some sort of heat/memory/cache issue here, gcc should not die under sig11, and sig11 is a pretty well known indicator of hardware problems. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message