From owner-freebsd-hackers Fri Mar 17 14:05:27 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA12328 for hackers-outgoing; Fri, 17 Mar 1995 14:05:27 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA12319 for ; Fri, 17 Mar 1995 14:05:21 -0800 Received: from geli.clusternet (rcarter.vip.best.com [204.156.137.2]) by shell1.best.com (8.6.10/8.6.5) with ESMTP id OAA13067 for ; Fri, 17 Mar 1995 14:05:01 -0800 Received: (from rcarter@localhost) by geli.clusternet (8.6.11/8.6.9) id OAA14843 for hackers@FreeBSD.org; Fri, 17 Mar 1995 14:03:54 -0800 Date: Fri, 17 Mar 1995 14:03:54 -0800 From: "Russell L. Carter" Message-Id: <199503172203.OAA14843@geli.clusternet> To: hackers@FreeBSD.org Subject: Re: Non Parity Ram 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. | | 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 :-) | I've got two 32MB systems running no-parity (an Intel 100MHZ Premiere and an ASUS P54SP4) with no problems at all for two months. At least as far as I can tell ;-) 4x32 simms have been a lot cheaper than 4x36 in the past, but they seem to be less so these days. Russell