From owner-freebsd-questions Tue Mar 28 05:58:44 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA12245 for questions-outgoing; Tue, 28 Mar 1995 05:58:44 -0800 Received: from disperse.demon.co.uk (disperse.demon.co.uk [158.152.1.77]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA12239 for ; Tue, 28 Mar 1995 05:58:42 -0800 Received: from post.demon.co.uk by disperse.demon.co.uk id aa06597; 28 Mar 95 14:56 GMT-60:00 Received: from palmer.demon.co.uk by post.demon.co.uk id aa26252; 28 Mar 95 14:56 GMT-60:00 Received: from localhost (gary@localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.9/8.6.9) with SMTP id OAA00284 ; Tue, 28 Mar 1995 14:23:42 +0100 X-Authentication-Warning: palmer.demon.co.uk: Host localhost didn't use HELO protocol To: bmk@dtr.com cc: Thomas Krebs , questions@FreeBSD.org Subject: Re: RAM parity error?? In-reply-to: Your message of "Tue, 28 Mar 1995 03:25:14 -0800." <199503281125.DAA00743@dtr.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <280.796397021.1@palmer.demon.co.uk> Date: Tue, 28 Mar 1995 14:23:41 +0100 Message-ID: <281.796397021@palmer.demon.co.uk> From: Gary Palmer Sender: questions-owner@FreeBSD.org Precedence: bulk In message <199503281125.DAA00743@dtr.com>, bmk@dtr.com writes: >I would guess that message comes from your BIOS, and not from FreeBSD - >but I could be mistaken. I would think that if FreeBSD detected an >error of this sort, it'd force a panic. The BIOS should be dead when FreeBSD is running. The parity errors come from /sys/i386/isa/isa.c. Look for `parity'. As to the cause - it varies from machine to machine I'm afraid :-( Gary