From owner-freebsd-hackers  Thu Aug 22  0:42:31 2002
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id E483A37B400; Thu, 22 Aug 2002 00:42:26 -0700 (PDT)
Received: from mail.imp.ch (mail.imp.ch [157.161.1.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id AF34643E42; Thu, 22 Aug 2002 00:42:25 -0700 (PDT)
	(envelope-from mb@imp.ch)
Received: from nbs.imp.ch (nbs.imp.ch [157.161.4.7])
	by mail.imp.ch (8.12.3/8.12.3) with ESMTP id g7M7gCnZ038958;
	Thu, 22 Aug 2002 09:42:12 +0200 (CEST)
	(envelope-from Martin.Blapp@imp.ch)
Received: from levais.imp.ch (levais.imp.ch [157.161.4.66])
	by nbs.imp.ch (8.12.3/8.12.3) with ESMTP id g7M7gCYW1044497;
	Thu, 22 Aug 2002 09:42:12 +0200 (MES)
Date: Thu, 22 Aug 2002 09:43:45 +0200 (CEST)
From: Martin Blapp <mb@imp.ch>
To: Don Lewis <dl-freebsd@catspoiler.org>
Cc: <marks@ripe.net>, <ktsin@acm.org>, <freebsd-current@FreeBSD.ORG>,
	<hackers@FreeBSD.ORG>
Subject: Memory corruption in CURRENT
In-Reply-To: <200208220704.g7M74Lwr035988@gw.catspoiler.org>
Message-ID: <20020822094025.L34509-100000@levais.imp.ch>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.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-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


Hi all,

I suspect all the SIG4 and SIG11 problems we see are due
memory corruption in CURRENT.

> In the latter case, the affected file looks like:
>
>   case HASH('^', 'e'):
>   case HASH('^', 'i'):
>   case HASH('^'  'o'):
> \xc0 case HASH('^', 'u'):
>  %case HADH('`', \xc0A'):
>   ^@ase HASH('`', 'E'):
>   case HASH('`', 'I'):
>   case HASH('`', 'O'):
>   case HASH('`', 'U'):
>
> The file is correct after a reboot, so the corruption was limited to the
> copy cached in RAM.

Thats memory corruption. I'm also not able anymore
to make 10 buildworlds (without -j, that triggers
panics in pmap code).

Bye the way, I'm experiencing this since about 4-5 months.

All hackers, please help to track this down.
Martin


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