From owner-freebsd-hackers Fri Mar 17 11:03:39 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA06335 for hackers-outgoing; Fri, 17 Mar 1995 11:03:39 -0800 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA06323 for ; Fri, 17 Mar 1995 11:03:36 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id LAA19237; Fri, 17 Mar 1995 11:03:09 -0800 From: "Rodney W. Grimes" Message-Id: <199503171903.LAA19237@gndrsh.aac.dev.com> Subject: Re: Non Parity Ram To: mmead@goof.com (matthew c. mead) Date: Fri, 17 Mar 1995 11:03:08 -0800 (PST) Cc: hackers@FreeBSD.org In-Reply-To: <199503171832.NAA08414@goof.com> from "matthew c. mead" at Mar 17, 95 01:32:52 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 638 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > What will FreeBSD do with Non Parity ram? I have some of this. I haven't > been getting parity errors or anything, but I'm kind of curious if it's going > to cause problems... If your motherboard supports non parity ram it will work, the real down side is that if a memory error does occur you wan't know about it as it will not generate a NMI so that FreeBSD can gracefully panic. Instead something will just go wrong some place, without a clue as to why it happened. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD