From owner-freebsd-stable  Tue Jul 15 15:29:59 1997
Return-Path: <owner-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA28336
          for stable-outgoing; Tue, 15 Jul 1997 15:29:59 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA28304;
          Tue, 15 Jul 1997 15:29:46 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id PAA21489;
	Tue, 15 Jul 1997 15:30:07 -0700 (PDT)
Message-Id: <199707152230.PAA21489@implode.root.com>
To: Philipp Reichmuth <chokepnt@prima.ruhr.de>
cc: stable@FreeBSD.ORG, FreeBSD Questions <freebsd-questions@FreeBSD.ORG>
Subject: Re: mw fails even more... 
In-reply-to: Your message of "Wed, 16 Jul 1997 01:32:51 +0200."
             <33CC08A3.41C67EA6@prima.ruhr.de> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 15 Jul 1997 15:30:07 -0700
Sender: owner-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>cc: Internal compiler error: program cc1 got fatal signal 11
...
>ASUS TX97E with AMD K6/200; 64 MB RAM (FPM 60ns and never had any

   There is a discussion going on in the -hardware list about K6 CPUs working
fine for a few weeks and then developing reliabilty problems just like you're
reporting above. In addition to a machine here that is having similar
problems, I've exchanged email with at least a half dozen people now who have
had same problems.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project