From owner-freebsd-hackers Fri Dec 28 14: 1:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 1078C37B41F; Fri, 28 Dec 2001 14:01:20 -0800 (PST) Received: from colt.ncptiddische.net (ppp-280.wobline.de [212.68.71.1]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fBSLm1802892; Fri, 28 Dec 2001 22:48:01 +0100 Received: from tisys.org (poison.ncptiddische.net [192.168.0.5]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fBSLm5X81694; Fri, 28 Dec 2001 22:48:05 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id fBSLlwn03935; Fri, 28 Dec 2001 22:47:58 +0100 (CET) (envelope-from nils) Date: Fri, 28 Dec 2001 22:47:58 +0100 From: Nils Holland To: Glenn Johnson Cc: Greg Lehey , FreeBSD Questions , FreeBSD Hackers Subject: Re: Does FreeBSD have a problem with some AMD processors? Message-ID: <20011228224758.B3860@tisys.org> References: <20011228181009.F95692@monorchid.lemis.com> <20011228204612.GA1226@gforce.johnson.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011228204612.GA1226@gforce.johnson.home>; from glennpj@charter.net on Fri, Dec 28, 2001 at 02:46:12PM -0600 X-Operating-System: FreeBSD poison.ncptiddische.net 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE X-Machine-Uptime: 10:30PM up 8:01, 1 user, load averages: 0.00, 0.00, 0.00 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Dec 28, 2001 at 02:46:12PM -0600, Glenn Johnson stood up and spoke: > As far as I can tell though if I set the memory clock to > 100MHz the problem goes away completely, or at least I have not observed > it happen yet. So it's PC133 RAM but only works properly at 100 Mhz? Well, I guess I have seen the same problem: I once had a system with a front side bus of 100 Mhz, and I could set the RAM clock to either "host clock" or "host click + 33 Mhz". Now, I choose the second method, because according to my calculation, a host clock of 100 Mhz plus an additional 33 Mhz are 133 Mhz, and thus just what my PC133 RAM wants. However, the system would run less than reliable with this setting, so I later set the RAM clock to "host clock", so 100 Mhz. I no longer own that system - I had these problems back in June... Anyway, for most memory problems, I have found the tool "memtest86" (http://www.memtest86.com) to be a good test. While, as far as I have heard, this utility does not detect *all* possible errors, it has often been able to give me good insight of the stability of my RAM and overall system. Greetings Nils -- Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message