From owner-freebsd-current@FreeBSD.ORG  Wed Jul 23 15:06:08 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 50A9B37B401
	for <freebsd-current@freebsd.org>;
	Wed, 23 Jul 2003 15:06:08 -0700 (PDT)
Received: from smtp.web.de (smtp02.web.de [217.72.192.151])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C30C043F75
	for <freebsd-current@freebsd.org>;
	Wed, 23 Jul 2003 15:06:07 -0700 (PDT)	(envelope-from g.w.k@web.de)
Received: from [217.232.165.187] (helo=[217.232.165.187])
	by smtp.web.de with asmtp (WEB.DE 4.99 #420)
	id 19fRkM-0001oC-00
	for freebsd-current@freebsd.org; Thu, 24 Jul 2003 00:06:07 +0200
From: "Georg-W. Koltermann" <g.w.k@web.de>
To: freebsd-current@freebsd.org
Content-Type: text/plain
Message-Id: <1058998043.628.77.camel@bat.localnet>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.3 
Date: 24 Jul 2003 00:07:23 +0200
Content-Transfer-Encoding: 7bit
Sender: g.w.k@web.de
Subject: still data corruption with 5.1-R on Intel Pentium 4
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jul 2003 22:06:08 -0000

There have been threads about data corruption in RAM on P4 and other
i386 machines on this list.  I also observed the problem, on my laptop
with 5.0-R.  It seemed to go away with 5.1-R, on the laptop.

Recently I upgraded my home PC which is a P4 2.0A from 4.8-R to 5.1-R. 
No problems at first.

Until I ran "portsdb -Uu".  I got a couple mysterious SIG4 and SIG11.
Just to be sure I rebooted and tried again, same result.  I rebooted
another time, this time with ACPI disabled, and tried again, still the
same.

Then I rebuilt my kernel with options DISABLE_PSE and DISABLE_PG_G, as
suggested by Terry in the old threads: Bingo, everything is fine now, no
more SIG4 or SIG11 during portsdb -Uu.

It seems the workarounds that we have in 5.1-R are not effective enough.
What do you think?

--
Regards,
Georg.