From owner-freebsd-stable Wed Aug 11 8:28:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gidgate.gid.co.uk (gidgate.gid.co.uk [193.123.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 864BC15531 for ; Wed, 11 Aug 1999 08:28:14 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.8.8/8.8.7) id QAA06530; Wed, 11 Aug 1999 16:26:43 +0100 (BST) (envelope-from rb) Message-Id: <3.0.6.32.19990811162641.007b8cb0@192.168.255.1> X-Sender: rbmail@192.168.255.1 X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 11 Aug 1999 16:26:41 +0100 To: tcobb@staff.circle.net From: Bob Bishop Subject: Re: On freezes in 3.2-Stable Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <307D63ED6749CF11AAE9005004461A5B4057@FREYA> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 10:42 11/08/99 -0400, tcobb@staff.circle.net wrote: >[tail of woe truncated] >HOWEVER, I've been able to avoid a freeze for the past >36 hours now by doing one simple thing -- removing the last >256MB ECC RAM stick out of the box, leaving it with only >768MB. > >The removed RAM has tested out just fine, so that leaves >one of two possibilities: > >1. Supermicro can't handle a full 1GB, despite their specs >OR >2. FreeBSD can't handle that much memory in a stable manner OR 3. Something is marginal on the motherboard, and it won't drive 4 RAM modules (assuming that was 4 x 256 you were running). -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message