From owner-freebsd-current@FreeBSD.ORG Thu Jan 22 18:50:09 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 115DF106567C for ; Thu, 22 Jan 2009 18:50:09 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id F19C88FC12 for ; Thu, 22 Jan 2009 18:50:08 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id BBF3A33C62 for ; Thu, 22 Jan 2009 10:50:08 -0800 (PST) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 575F733C5B for ; Thu, 22 Jan 2009 10:50:08 -0800 (PST) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18808.49120.167837.490082@almost.alerce.com> Date: Thu, 22 Jan 2009 10:50:08 -0800 To: freebsd-current@freebsd.org X-Mailer: VM 7.19 under Emacs 22.1.50.1 X-Virus-Scanned: ClamAV using ClamSMTP X-Mailman-Approved-At: Thu, 22 Jan 2009 19:12:38 +0000 Subject: Steps to debug memory/motherboard (Via VB8001) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 18:50:10 -0000 I have a Via VB8001 running 8.0-CURRENT using ZFS on a pair of SATA drives. It has two memory slots, and I have 2x2GB of Kingston PC2 5300 memory (KVR667D2N5K2/4G) that I think is correct. I can run with either of the DIMMs in the first slot and am able to build and install world and kernel. If I populate both slots then I can run for a bit (e.g. make buildkernel) before I end up in the debugger or with the build bombing out with a message about "bad address". This happens no matter which DIMM is in which slot. With both DIMMs installed the system only reports 3GB to the BIOS and to FreeBSD, others have reported this and it seems to be a limitation of the BIOS and the integrated video. The fact that the DIMMs work in isolation and I have problems independent of which one goes in which slot suggests that the problem is either: a) with the motherboard b) with how -CURRENT sets up or drives the hardware. c) bad memory that only shows up when both DIMMs are in use. I didn't get the RAM and the board from the same vendor, so I'm kind of expecting some finger pointing. Left to my own devices, I'd blame the motherboard and try to get it swapped. Is it more likely to be a memory problem? A -CURRENT problem? Thanks, g.