From owner-freebsd-current Wed Apr 26 12: 7:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 6425537BCC3 for ; Wed, 26 Apr 2000 12:07:48 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id OAA11072; Wed, 26 Apr 2000 14:07:42 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Wed, 26 Apr 2000 14:07:42 -0500 (CDT) From: David Scheidt To: Matthew Jacob Cc: Brian Somers , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: cc1 sig 11'ing recently? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Apr 2000, Matthew Jacob wrote: > > Umm- doubt it, but I'll check. This system has been fine for the last 18 > months and runs everything else just peachy. > Sudden SIGSEGVs are almost always the result of failed memory. The fact that the machine worked fine for 18 months doesn't mean anything. Replace the memory and your problems will likely go away. If they don't, it's likely that the problem is cooling, processor cache, or a bad motherboard memory bus. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message