From owner-freebsd-current  Thu Aug 22  2: 9:34 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 E8CCF37B401; Thu, 22 Aug 2002 02:09:30 -0700 (PDT)
Received: from freebsd.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id EB89743E4A; Thu, 22 Aug 2002 02:09:29 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.12.5/8.12.5) id g7M99NcS077303;
	Thu, 22 Aug 2002 11:09:23 +0200 (CEST)
	(envelope-from sos)
From: Soeren Schmidt <sos@freebsd.dk>
Message-Id: <200208220909.g7M99NcS077303@freebsd.dk>
Subject: Re: Memory corruption in CURRENT
In-Reply-To: <20020822094025.L34509-100000@levais.imp.ch>
To: Martin Blapp <mb@imp.ch>
Date: Thu, 22 Aug 2002 11:09:22 +0200 (CEST)
Cc: Don Lewis <dl-freebsd@catspoiler.org>, marks@ripe.net,
	ktsin@acm.org, freebsd-current@FreeBSD.ORG, hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL98b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=ISO-8859-1
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

It seems Martin Blapp wrote:
> 
> Hi all,
> 
> I suspect all the SIG4 and SIG11 problems we see are due
> memory corruption in CURRENT.
....
> > 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.

Hmm, I haven't seen this at all, but I've just started buildworld loops on
two machines here, but I normally do at least a couble buildworlds a day
and I havn't notice problems like the above (but plenty of bad commits etc).

However, this kind of problem in most cases spells bad HW to me,
ie subspec RAM, poor powersupply, badly cooled CPU, overclocking etc etc...

-Søren

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