From owner-freebsd-hardware Mon Sep 15 07:08:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA00927 for hardware-outgoing; Mon, 15 Sep 1997 07:08:17 -0700 (PDT) Received: from news.nacamar.de (news.nacamar.de [194.162.162.210]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA00918 for ; Mon, 15 Sep 1997 07:08:13 -0700 (PDT) Received: from newsfeed (newsfeed.nacamar.de [194.162.162.196]) by news.nacamar.de (8.8.7/8.8.6) with SMTP id QAA15526 for ; Mon, 15 Sep 1997 16:08:07 +0200 (CEST) Message-Id: <3.0.3.32.19970915160712.00b69930@mail.nacamar.de> X-Sender: petzi@mail.nacamar.de X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 15 Sep 1997 16:07:12 +0200 To: hardware@freebsd.org From: Michael Beckmann Subject: Parity trouble with Asus mainboard Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I had installed 8 x 32 MB parity SIMMs in an Asus P65UP5 Rev. 2.04 mainboard with Pentium Pro card P6ND in it. The system is equipped with one PPro 200 CPU. Unfortunately, when I install 4, 6 or 8 of these SIMMs, FreeBSD gives me a parity error and panics directly after the copyright notice during boot. With 2 x 32 MB, it seems to run OK. This, however, happens only when I enable ECC in the BIOS. When I disable ECC/parity, the system runs fine with 256 MB installed. I made world on the latest 2.2-stable in this configuration, no problem. I also tried the same SIMMs in a Gigabyte 586 HX board, and there I can boot and run just fine with ECC enabled in the BIOS (it's an NT system, though). Any ideas ? It doesn't look to me like the SIMMs were faulty. Maybe a problem with the parity chips ? I also exchanged the mainboard with another one of the same type, but found the same problem. Michael