From owner-freebsd-hackers Thu Sep 24 08:44:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18126 for freebsd-hackers-outgoing; Thu, 24 Sep 1998 08:44:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sparks.net (gw.sparks.net [209.222.120.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA18120 for ; Thu, 24 Sep 1998 08:44:21 -0700 (PDT) (envelope-from david@sparks.net) Received: from david by sparks.net with smtp (Exim 1.62 #5) id 0zMDYY-0005p3-00; Thu, 24 Sep 1998 11:43:46 -0400 Date: Thu, 24 Sep 1998 11:43:45 -0400 (EDT) From: To: Chuck Youse cc: Drew Baxter , freebsd-hackers@FreeBSD.ORG Subject: Re: AMD K6-2/300 problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 24 Sep 1998, Chuck Youse wrote: > Generally this problem can be associated with defective memory. Or, in > some systems, mixing memory types. > > I had a Dual P2/300 system that exhibited similar symptoms with regard to > compilations. When I removed the a pair of 16 meg SIMMs (leaving just the > 64MB SDRAM) the problem went away. The SIMMs tested OK, so the problems > must have resulted from the mixture. A mixture is generally a bad things I believe. In this case I'm pretty certain that it's slow memory. I slowed the bus down to 83 MHz amd bumped the multiplier to four, resulting in a CPU rate of 333 MHz. This seems to work fine, so I'll run with it for a while. Thanks for all the help. Its nice to know it's not a K6 compatibility problem:) --- David ---------------------------------------------------------------------------- It's *amazing* what one can accomplish when one doesn't know what one can't do! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message