From owner-freebsd-hackers Fri Mar 17 11:40:23 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA07775 for hackers-outgoing; Fri, 17 Mar 1995 11:40:23 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA07769 for ; Fri, 17 Mar 1995 11:40:21 -0800 Received: (from mmead@localhost) by goof.com (8.6.11/8.6.9) id OAA00756; Fri, 17 Mar 1995 14:40:10 -0500 From: "matthew c. mead" Message-Id: <199503171940.OAA00756@goof.com> Subject: Re: Non Parity Ram To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Fri, 17 Mar 1995 14:40:09 -0500 (EST) Cc: hackers@FreeBSD.org In-Reply-To: <199503171903.LAA19237@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Mar 17, 95 11:03:08 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1026 Sender: hackers-owner@FreeBSD.org Precedence: bulk Rodney W. Grimes wrote: > > > > 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. Hmm. The ram seems to be behaving (no odd problems), and I like having 52M vs. 20M, so I'm going to try to live with it and offload it on some dos user for parity ram at some point :-) -matt -- Matthew C. Mead -> Virginia Tech Center for Transportation Research - -> Multiple Platform System and Network Administration Work Related -> mmead@ctr.vt.edu | mmead@goof.com <- All Other ---- ------- WWW -> http://www.goof.com/~mmead --- -----