From owner-freebsd-current  Wed Sep 18 15:40: 1 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DBF6C37B401
	for <current@FreeBSD.ORG>; Wed, 18 Sep 2002 15:39:59 -0700 (PDT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DD14F43E4A
	for <current@FreeBSD.ORG>; Wed, 18 Sep 2002 15:39:58 -0700 (PDT)
	(envelope-from dlewis@slicex.com)
Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8IMdowr020533;
	Wed, 18 Sep 2002 15:39:54 -0700 (PDT)
	(envelope-from dlewis@slicex.com)
Message-Id: <200209182239.g8IMdowr020533@gw.catspoiler.org>
Date: Wed, 18 Sep 2002 15:39:49 -0700 (PDT)
From: Don Lewis <dlewis@slicex.com>
Subject: Re: Crashdumps available for download ... please help
To: wollman@lcs.mit.edu
Cc: mb@imp.ch, current@FreeBSD.ORG
In-Reply-To: <200209181532.g8IFWfMC040815@khavrinen.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On 18 Sep, Garrett Wollman wrote:
> <<On Wed, 18 Sep 2002 08:27:08 +0200 (CEST), Martin Blapp <mb@imp.ch> said:
> 
>> 10. Upgraded to gcc3.2. I was seeing now some SIG11 during builds,
>>     and - panics ! Softupdates and fs panics mostly. I turned off
>>     softupdates. The panic was different, but all the time it was
>>     in mmap.
> 
> I'm not seeing panics, but I am seeing memory corruption causing about
> every third buildworld to fail.  Usually this affects `cc1' or `ld',
> but last night I saw corruption in a source file.

That sounds exactly like what I saw until I added

# memory corruption workaround?
options         DISABLE_PSE
options         DISABLE_PG_G

to my kernel configuration.  Since then the system has been pretty solid
except for a few NFS issues that I've identified, and a couple of
failures during openoffice builds that have been very difficult to
reproduce.

Martin is already using these options.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message