From owner-freebsd-questions@FreeBSD.ORG Thu Jan 12 19:31:43 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4206516A41F for ; Thu, 12 Jan 2006 19:31:43 +0000 (GMT) (envelope-from njt@ayvali.org) Received: from sanddollar.geekisp.com (sanddollar.geekisp.com [204.89.131.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 816B443D45 for ; Thu, 12 Jan 2006 19:31:42 +0000 (GMT) (envelope-from njt@ayvali.org) Received: (qmail 31586 invoked by uid 1003); 12 Jan 2006 19:31:41 -0000 Received: from clam.int.geekisp.com (HELO clam.geekisp.com) (192.168.4.38) by mail.geekisp.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 12 Jan 2006 19:31:41 -0000 Received: from clam.geekisp.com (njt@localhost.geekisp.com [127.0.0.1]) by clam.geekisp.com (8.13.3/8.12.11) with ESMTP id k0CJVfm0007774; Thu, 12 Jan 2006 14:31:41 -0500 (EST) Received: (from njt@localhost) by clam.geekisp.com (8.13.3/8.13.3/Submit) id k0CJVerK009322; Thu, 12 Jan 2006 14:31:40 -0500 (EST) X-Authentication-Warning: clam.geekisp.com: njt set sender to njt@ayvali.org using -f Date: Thu, 12 Jan 2006 14:31:40 -0500 From: "N.J. Thomas" To: Brad Marsh Message-ID: <20060112193140.GE2451@ayvali.org> References: <20060112182206.GB2451@ayvali.org> <20060112190930.86187.qmail@web31013.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060112190930.86187.qmail@web31013.mail.mud.yahoo.com> Mail-Folloup-To: freebsd-questions@freebsd.org User-Agent: Mutt/1.5.9i Cc: freebsd-questions@freebsd.org Subject: Re: Help with panic: vm_fault X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2006 19:31:43 -0000 * Brad Marsh [2006-01-12 11:09:29 -0800]: > OK...in agreement, I've read that memory modules will sometimes work > in pairs, not individually Older memory/systems used to only take memory that worked in pairs, newer ones shouldn't have that problem. In the worst case, it may accept a single module, but maybe not run as fast as it would with a pair. But my memory-fu isn't up to date, and perhaps someone could correct me. > or singly, not in pairs... This should never be the case. If your memory is acceptable one module at a time, why wouldn't the system accept two? Thomas -- N.J. Thomas njt@ayvali.org Etiamsi occiderit me, in ipso sperabo