From owner-freebsd-stable Mon May 7 13:56:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from beastie.saturn-tech.com (beastie.saturn-tech.com [207.229.19.136]) by hub.freebsd.org (Postfix) with ESMTP id 0D9BC37B422 for ; Mon, 7 May 2001 13:56:27 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by beastie.saturn-tech.com (8.11.1/8.11.0) with ESMTP id f47Mex301651; Mon, 7 May 2001 16:40:59 -0600 (MDT) (envelope-from drussell@saturn-tech.com) X-Authentication-Warning: beastie.saturn-tech.com: drussell owned process doing -bs Date: Mon, 7 May 2001 16:40:59 -0600 (MDT) From: Doug Russell To: Jonathan Belson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Lockups with -Stable on Athlon In-Reply-To: <3AF6EE86.FC021C05@witchspace.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 May 2001, Jonathan Belson wrote: > machine - but again, why do the other OSes work fine? Because they can't possibly push your hardware as hard as FreeBSD does. Adding an extra clock cycle of net delay in one little operation is all it might take to make one of these timing issues never show up on another OS. (Not to mention, they don't usually stay up long enough to find out. :) ) All of these people who are seeing the same type of crashing problem, are all probably using memory that just isn't up to snuff. I've seen this NUMEROUS times on Athlons (I use mainly A7Vx boards). EVERY SINGLE TIME, changing to truly good RAM (ie. Micron, perhaps Infineon), has cured the problem. Most Hyundai I've seen, for example, will run fine at 100 MHz in the Athlon, but not at 133 MHz, but will work fine in many other boards at 133 MHz. Of course, I can usually make Windows crash with the poor memory, too. Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message