From owner-freebsd-stable Mon May 1 16:18: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id 522FB37B983 for ; Mon, 1 May 2000 16:18:05 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA04321; Mon, 1 May 2000 16:26:22 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005012326.QAA04321@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Daniel Frazier Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make buildworld fails... In-reply-to: Your message of "Mon, 01 May 2000 19:12:56 EDT." <390E0F78.AE694C64@magpage.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 May 2000 16:26:22 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Chad R. Larson" wrote: > > > Bad RAM, bad disk, generally bad hardware, cosmic rays, bug in FreeBSD > > > (probably in that order of probability :-) > > > > Bad RAM controller, bad DMA controller, bad RAM chips. > > > > Wow, not quite the answers I was looking for, but at least you've all > given me an idea of what to look for. Thanks for your help. By the > way, do you know of any RAM stress test/diagnostic utility that could > help narrow this down? You're running it. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message