From owner-freebsd-stable Mon May 7 12:59:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tepid.osl.fast.no (tepid.osl.fast.no [213.188.9.130]) by hub.freebsd.org (Postfix) with ESMTP id 6906037B42C for ; Mon, 7 May 2001 12:59:12 -0700 (PDT) (envelope-from Raymond.Wiker@fast.no) Received: from raw.grenland.fast.no.fast.no (fw-oslo.fast.no [213.188.9.129]) by tepid.osl.fast.no (8.9.3/8.9.1) with ESMTP id TAA67515; Mon, 7 May 2001 19:59:04 GMT (envelope-from Raymond.Wiker@fast.no) From: Raymond Wiker MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15094.65159.213219.918840@raw.grenland.fast.no> Date: Mon, 7 May 2001 21:59:03 +0200 To: freebsd-stable@FreeBSD.ORG Subject: Re: Lockups with -Stable on Athlon In-Reply-To: <20010507112335U.jkh@osd.bsdi.com> References: <200105071556.f47Fu1N16065@quarter.csl.sri.com> <20010507112335U.jkh@osd.bsdi.com> X-Mailer: VM 6.92 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard writes: > Odd. What sort of LISP environment are you running? I've got 4.3 > running on my 900MHz Athlon + ASUS K7 motherboard and it works great > and has for a long time. Are you running a custom kernel > configuration? I'm using an EPOX 8KTA3+ with a Duron 700 (7x100), a 256MB 133MHz SIMM and a 128MB 100MHz SIMM. I noticed that the actual RAM chips on the SIMMS were the same speed (7.5ns), so I forced the BIOS to use the 133MHz timing. With this setup, I saw the same behaviour as Fred Gilham reports. Sooo, I guess it could be either a marginal RAM chip, or possibly some slight incompatibility with the motherboard. (I've seen some talk on a resgroup dedicated to the EPOX 8KTA3+ that it's possible to configure the VIA KT133A chipset for a higher "RAM drive strength"; this is supposed to work with a wider range of SIMMS.) //Raymond. -- Raymond Wiker Raymond.Wiker@fast.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message