From owner-freebsd-questions Sun Jan 30 13: 5:11 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.alpha.net.au (mail2.alpha.net.au [203.41.44.8]) by hub.freebsd.org (Postfix) with ESMTP id 0F9AB151A1 for ; Sun, 30 Jan 2000 13:05:08 -0800 (PST) (envelope-from dannyh@idx.com.au) Received: from psych ([203.41.44.152]) by mail.alpha.net.au (8.9.3/8.9.3) with SMTP id IAA24613; Mon, 31 Jan 2000 08:06:00 +1100 Message-Id: <3.0.32.20000131080512.007749ac@idx.com.au> X-Sender: dannyh@idx.com.au X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 31 Jan 2000 08:05:46 +1100 To: "Kevin Oberman" , R Joseph Wright From: Danny Subject: Re: Why Doesn't XFree86 Upgrade Properly (still no resolution) Cc: questions@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -I did what you mentioned below with the ports - upragding to the latest XFree86 - then ran XF86Setup I get the Kernel Dump. - Usually I would suspect faulty hardware put it doesn't give me any problems using Linux 6.1 Question 1)What else can I try? 2)How do I fix the problem? At 07:30 28/01/00 -0800, Kevin Oberman wrote: >As I mentioned in my last message, my problem with bad RAM was on my >brand new system. > >Memory (and, to a lesser extent, other solid-state components) will >typically fail in the first 90 days or after several years. This is >probably more true of memory than most chips because of the very dense >nature of the chips. (I don't think I want to get into an explanation >of atomic migration and the like. I really don't fully understand it >myself and I'd just be parroting a friend who is a solid-state >physicist.) > >In any case, memory that lasts for 6 months is probably good for >years. This is why many Mil-specs and NASA specs require extended >burn-in periods for all solid-state components. > >If you have two DIMMs, pull one. FreeBSD can get by with 16 or 32 MB >with no problems (although some operation may slow down). If it still >crashes, put that one back and pull the other. !!!Follow proper >anti-static procedures!!! > >R. Kevin Oberman, Network Engineer >Energy Sciences Network (ESnet) >Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) >E-mail: oberman@es.net Phone: +1 510 486-8634 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message