From owner-freebsd-hardware Fri Nov 20 08:27:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19851 for freebsd-hardware-outgoing; Fri, 20 Nov 1998 08:27:42 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from rain.futuresouth.com (rain.futuresouth.com [198.79.79.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19822 for ; Fri, 20 Nov 1998 08:27:10 -0800 (PST) (envelope-from stormy@rain.futuresouth.com) Received: (from stormy@localhost) by rain.futuresouth.com (8.9.1/8.9.1) id KAA05268 for freebsd-hardware@FreeBSD.ORG; Thu, 19 Nov 1998 10:27:38 -0600 (CST) (envelope-from stormy) Message-ID: <19981119102738.C4105@futuresouth.com> Date: Thu, 19 Nov 1998 10:27:38 -0600 From: Stormy Henderson To: freebsd-hardware@FreeBSD.ORG Subject: Re: Instability... Mail-Followup-To: freebsd-hardware@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A happy camper (Stefan Lindgren, s.lindgren@telia.com) once wrote... > The could run for a day or two(or 20 min) and then it's just get fatal > trap 12 and the kernel dumps. It doesn't matter if I run in dual or uni > CPU mode. When I compile something, cc sometimes stop becuase of > internal error. The GCC signal 11 is your problem, it hints that you have hardware problems, most likely RAM or cache. Read the FAQ entry on signal 11; it will direct you to a separate FAQ devoted solely to fixing this problem. Be happy... -- http://www.futuresouth.com/~stormy/signature.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message