From owner-freebsd-hardware Thu Sep 21 9:39:31 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id B77A437B424 for ; Thu, 21 Sep 2000 09:39:28 -0700 (PDT) Received: from sharky (adsl-151-202-75-61.bellatlantic.net [151.202.75.61]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id KAA66176; Thu, 21 Sep 2000 10:36:31 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200009211636.KAA66176@mail.fpsn.net> From: "Simon" To: "chris@ritc.co.uk" , "Cliff Rowley" , "Dale Chulhan - Work" Cc: "freebsd-hardware@FreeBSD.ORG" Date: Thu, 21 Sep 2000 12:42:14 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) In-Reply-To: <000a01c023e7$803469b0$200101c8@SOL> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Memory detection problems Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've once decided to give ValueRAM a spin. It took quite few days to figure out what was causing the random panics - buildworld, etc... wouldn't fail. Whatever you do, do not put ValueRAM into server that you want to have good uptime on. -Simon On Thu, 21 Sep 2000 12:17:54 -0400, Dale Chulhan - Work wrote: >> I had exactly the same thing a few months back. I replaced my RAM and >> I've never seen it since. >its quite an interesting problem ... could any one give a techie explanation >to it? > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message