From owner-freebsd-questions Sun Jun 16 17:15:29 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA00813 for questions-outgoing; Sun, 16 Jun 1996 17:15:29 -0700 (PDT) Received: from mailhub.aros.net (mailhub.aros.net [205.164.111.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA00808 for ; Sun, 16 Jun 1996 17:15:27 -0700 (PDT) Received: from terra.aros.net (terra.aros.net [205.164.111.10]) by mailhub.aros.net (8.7.5/Unknown) with ESMTP id SAA05608; Sun, 16 Jun 1996 18:55:50 -0600 (MDT) Received: (from angio@localhost) by terra.aros.net (8.7.5/8.6.12) id SAA23695; Sun, 16 Jun 1996 18:15:23 -0600 From: Dave Andersen Message-Id: <199606170015.SAA23695@terra.aros.net> Subject: Re: -current SNAP installation panics To: dwhite@riley-net170-164.uoregon.edu (Doug White) Date: Sun, 16 Jun 1996 18:15:23 -0600 (MDT) Cc: questions@freebsd.org In-Reply-To: <199606150851.BAA00996@gdi.uoregon.edu> from "Doug White" at Jun 15, 96 01:51:24 am X-Mailer: ELM [version 2.4 PL25 PGP2] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Lo and behold, Doug White once said: > > -------- > > My $.02 says that I have a hardware problem, most likely dead memory, > > but I'm wondering if anyone has a more precise idea before I start > > strangling my supplier and asking for a replacement? > > Always a good guess :-) > > > It still panics with both the onboard and external caches disabled. > > It's a P133, triton chipset/award bios, 2 XP3125 quantum grand-prix > > (oops) 2gb HDs, 32 megs of 60-ns non-edo ram, adaptec 2940W controller, > > off-brand PCI video card. > > > > Clues? Memory? > > Panic details? (error message, panic code, etc.) It's not quoted in the your message, but in my original I stated that I wasn't including them because they varied -- I never got the same kernel panic twice. Different routines, different processes, different stack pointers. I took the easy way out and gutted another of my computers for its RAM. Presto, working perfectly. I'm just very relieved it wasn't the motherboard. (Past -questions and -hackers archive messages from Mike Smith indicate that problems of that nature are most likely a) memory, b) cache memory, or c) a horked motherboard. I wasn't in the mood to open the case up, because the computer is from a new supplier, and I wans't sure what their policies were w.r.t. the warranty were. -Dave -- angio@aros.net Complete virtual hosting and business-oriented system administration Internet services. (WWW, FTP, email) http://www.aros.net/ http://www.aros.net/about/virtual "There are only two industries that refer to their customers as 'users'."