From owner-freebsd-stable Wed Aug 11 12:19: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id EB45E155FB for ; Wed, 11 Aug 1999 12:19:05 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Wed, 11 Aug 1999 15:13:57 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B4069@FREYA> From: tcobb@staff.circle.net To: jkh@zippy.cdrom.com Cc: freebsd-stable@FreeBSD.ORG Subject: RE: On freezes in 3.2-Stable Date: Wed, 11 Aug 1999 15:13:50 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It happened with TWO Supermicro motherboards, one a P6SBU the other a P6DBU (one dual, one single). Both of these boards had four sticks of RAM in them before, but just 128's. Could be the electrical issue with more chips on the 256's. So, the consensus is that no adjustments are necessary for FreeBSD to support 1GB or greater? -Troy Cobb Circle Net, Inc. http://www.circle.net > I'm virtually certain thta this is a bogus motherboard. I know of a > number of systems running 1GB of memory that are perfectly stable > (including the quad processor Xeon at WC we use for > testing) just as I > know of several situations in the past were a motherboard completely > fell over after having all of its SIMM sockets populated. > As someone > else noted, there are often electrical limitations which present > themselves only when you stuff the board full of RAM. It > would be an > easy test to simply swap this motherboard and move the > memory back in. > > Also, how did you test the memory? With a hardware tester, I hope, > since all software memory tests are inherently bogus. Don't trust > them to tell you anything more than the fact that there's > power to the > memory. :) > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message