From owner-freebsd-current@FreeBSD.ORG Sat May 10 14:09:17 2003 Return-Path: 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 C33FB37B401 for ; Sat, 10 May 2003 14:09:17 -0700 (PDT) Received: from remt20.cluster1.charter.net (remt20.cluster1.charter.net [209.225.8.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9DE643FAF for ; Sat, 10 May 2003 14:09:16 -0700 (PDT) (envelope-from glennpj@charter.net) Received: from [24.158.214.251] (HELO gforce.johnson.home) by remt20.cluster1.charter.net (CommuniGate Pro SMTP 4.0.6) with ESMTP id 24413774; Sat, 10 May 2003 17:09:15 -0400 Received: from gforce.johnson.home (localhost [127.0.0.1]) by gforce.johnson.home (8.12.9/8.12.9) with ESMTP id h4AL9BEi020910; Sat, 10 May 2003 16:09:11 -0500 (CDT) (envelope-from glenn@gforce.johnson.home) Received: (from glenn@localhost) by gforce.johnson.home (8.12.9/8.12.9/Submit) id h4AL9AOK020903; Sat, 10 May 2003 16:09:10 -0500 (CDT) From: Glenn Johnson Date: Sat, 10 May 2003 16:09:10 -0500 To: Terry Lambert Message-ID: <20030510210909.GA10081@gforce.johnson.home> Mail-Followup-To: Terry Lambert , Heiko Schaefer , freebsd-current@freebsd.org References: <3EBC6C6A.1040602@myrealbox.com> <20030510130934.R93229@daneel.foundation.hs> <20030510203854.E93229@daneel.foundation.hs> <3EBD50D7.88A78B48@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EBD50D7.88A78B48@mindspring.com> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: Heiko Schaefer Subject: Re: data corruption with DISABLE_PSE+DISABLE_PG_G: unrelated X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2003 21:09:18 -0000 On Sat, May 10, 2003 at 12:19:51PM -0700, Terry Lambert wrote: > Heiko Schaefer wrote: > > > i'm sorry, my mail was probably a bit confusing. since it has been > > pointed out to me, i am running -current kernels with > > > > options DISABLE_PSE > > options DISABLE_PG_G > > > > enabled. > > > > what i am asking myself: > > is there any chance that i still get any data corruption because of > > the issues that you write about in some configuration ?! > > No. Not with thouse flags set. If you are getting data corruption > with the flags set, then you have some other problem, most likely > hardware. > > > > because with the 512mb (ddr) ram (which might or might not be > > defective) i get data corruption, while with another 256mb (sdr) > > ram, i apparently don't. > > At Whistle, we had a number of issues with matched simms; the > simms from one manufacturer were not good vs. another, supposedly > identically rated part. > > There's also the possibility that the RAM speed is too slow for your > FSB speed. You should be careful here, because not all motherboards > are able to detect this mismatch. I recently set up 6 AMD AthlonMP-2400+ systems, each with dual processors. I put Corsair memory (256MB) in them which I feel is a good brand. On two of the systems, I had to underclock them to get them stable. They went from 2400+ to 2100+, I forget what the exact clock speeds are. I was getting memory errors at "normal" speed. The machines would core dump on certain processes and it was very reproducible. In light of this discussion, I am wondering if I add the two kernel options under discussion if I could bring those machines back up to their rated speeds and have them be stable. Any thoughts on that? As an adjunct to that, would it be wise to put those options in regardless? Will the patches by Bosco be committed to the tree or is this too controversial? Thanks. -- Glenn Johnson glennpj@charter.net