From owner-freebsd-hardware Thu Jan 23 09:41:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA01570 for hardware-outgoing; Thu, 23 Jan 1997 09:41:07 -0800 (PST) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01565 for ; Thu, 23 Jan 1997 09:41:05 -0800 (PST) Received: from Mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.2/8.8.2-biteme) with ESMTP id LAA19931; Thu, 23 Jan 1997 11:41:03 -0600 (CST) Received: from Jupiter.Mcs.Net (jonas@Jupiter.mcs.net [192.160.127.88]) by Mailbox.mcs.com (8.8.5/8.8.2) with ESMTP id LAA06528; Thu, 23 Jan 1997 11:41:02 -0600 (CST) Received: (from jonas@localhost) by Jupiter.Mcs.Net (8.8.5/8.8.2) id LAA20054; Thu, 23 Jan 1997 11:41:01 -0600 (CST) From: Lars Jonas Olsson Message-Id: <199701231741.LAA20054@Jupiter.Mcs.Net> Subject: Re: DX4-100 and sig-11's To: chuckr@glue.umd.edu (Chuck Robey) Date: Thu, 23 Jan 1997 11:41:01 -0600 (CST) Cc: jonas@mcs.net, hardware@freebsd.org In-Reply-To: from "Chuck Robey" at Jan 23, 97 12:21:59 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK, I guess MemTest-86 isn't that great... I pulled one SIMM and it seems to work now. Jonas > > On Thu, 23 Jan 1997, Lars Jonas Olsson wrote: > > > I'm testing an older 486DX4-100 computer with FreeBSD. I've run85 > > cycles of memtest-86 on it with no problem, but FreeBSD dies when > > starting up (after npx probe). > > The system has a PVI-486SP3 motherboard, Award BIOS, 3 PCI slots, SiS > > 85C496 and 85X497 chipset and Intel DX4 A80486DX4100 SK051. The CPU > > has a "TOUCH H9512" (CPU made before Dec. 1995) sticker on it. Any > > ideas? The BIOS will let me choose write-thru or write-back for the > > caches but no disable. I've tried both options. > > Point 1: There is NO program whatsoever, under any operating system, > that does an even slightly reliable job of testing memory, > so disregard the memtest results. > Point 2: There IS a reliable memory test method, it involved using > a hardware based memory tester. Most vendors of memory > either have one or have access to one, so you have to ask > them to do your testing. > Point 3: Unix operating systems (as a class, not just FreeBSD) push > memory much harder than any dos program, and will easily > catch problems that are invisible to dos memory checkers. > Point 4: Altho they _do_ catch memory problems, Unix OSs are miserable > at telling you _where_ the problem is; see Point 2. > > The FreeBSD OS is solid, so if it's bombing, you have a hardware problem. > I'm not saying it's memory, perhaps something else is set up wrong. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 9120 Edmonston Ct #302 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > >