From owner-freebsd-hackers  Wed Sep 27 01:22:01 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id BAA19835
          for hackers-outgoing; Wed, 27 Sep 1995 01:22:01 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA19830
          for <hackers@freebsd.org>; Wed, 27 Sep 1995 01:21:54 -0700
Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id BAA11660; Wed, 27 Sep 1995 01:20:22 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id BAA00147; Wed, 27 Sep 1995 01:22:54 -0700
Message-Id: <199509270822.BAA00147@corbin.Root.COM>
To: Mark Murray <mark@grondar.za>
cc: hackers@freebsd.org
Subject: Re: make world on FreeBSD-stable impossible. cc1: ... signal 11 
In-reply-to: Your message of "Wed, 27 Sep 95 09:53:01 +0200."
             <199509270753.JAA07983@grumble.grondar.za> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Wed, 27 Sep 1995 01:22:54 -0700
Sender: owner-hackers@freebsd.org
Precedence: bulk

>> >Someone with a working -stable here ?! Since weeks unable to
>> >get a FreeBSD release compiled without that messages like:
>> >
>> >internal compiler error .... signal 11 ...
>> >
>> >Started with 2.0.5R ... compiled the stable kernel because of
>> >AHA 2940 problems ... and what now ???
>> >
>> >How can I help to track down the problem ?
>
>I have this problem too. I loaded 2.0.5, loaded the 2.1-stable sources,
>and as soon as 2.1-stable code is used (during the make world), it falls
>over. A temporary fix it to copy 2.1-current /usr/libexec/* to this machine.

   Please describe your machines in detail...output of dmesg would be a good
start.
   This sounds similar to the bug that was recently fixed in 2.2, but the code
in 2.1 is very different and should not be suseptible to this. The VFS cluster
code in 2.1 has not changed since 2.0.5.

>At the same spot for me. I was suspecting memory/cache problems, so far I
>have ruled out the cache.

   There was one other report about things dieing when one of the shared
libraries got out of sync, but after that was fixed the problems went away.
If you have the ability to try 2.1-stable on different hardware, but with
the same disk drive and binaries, this might help isolate the problem.
   It might also help if you could install the new 0922 snapshot.

-DG