From owner-freebsd-current@FreeBSD.ORG Sat May 10 14:12:54 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 93B9C37B401 for ; Sat, 10 May 2003 14:12:54 -0700 (PDT) Received: from critter.freebsd.dk (port757.uc1-esp.isdn-lan.cybercity.dk [212.242.98.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32D3943FDD for ; Sat, 10 May 2003 14:12:51 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h4ALCe56091597; Sat, 10 May 2003 23:12:41 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: Glenn Johnson From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 10 May 2003 16:09:10 CDT." <20030510210909.GA10081@gforce.johnson.home> Date: Sat, 10 May 2003 23:12:40 +0200 Message-ID: <91596.1052601160@critter.freebsd.dk> cc: Heiko Schaefer cc: freebsd-current@freebsd.org 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:12:54 -0000 In message <20030510210909.GA10081@gforce.johnson.home>, Glenn Johnson writes: >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? When I got my dual AthlonMP system, I had a hell of a time getting it stable. There were one particular stick of RAM it just would run with. I tried underclocking, extra cooling, rearranging ram sticks you name it, but always the same result. Then I flashed to the latest BIOS, and it's been stable as a rock since then. The BIOS update had no mention of anthing even remotely in that area. So, if nothing else, make sure you have your BIOS up to date. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.