From owner-freebsd-amd64@FreeBSD.ORG Wed Jul 27 22:44:18 2011 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8093B106566B for ; Wed, 27 Jul 2011 22:44:18 +0000 (UTC) (envelope-from tim.newsham@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3A6058FC1E for ; Wed, 27 Jul 2011 22:44:17 +0000 (UTC) Received: by qwc9 with SMTP id 9so1489599qwc.13 for ; Wed, 27 Jul 2011 15:44:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=yNTDdau+eFWrcphpU8e4Z8vlMQQ0DLT/6t7sVzm+oo0=; b=tmpc9Bpd4NfvUxY5VngfhD1JJnZhge22JhtPJ+b2HBfGMIcxHV3F0H5uQzGREUVGqh 7CgfukQMWgMC5aejgXna7Nqg+be28FKx/2CEx0deQtG2vI/HKUX0yZGViJrNCQrdKe7t 2Vjtad2ss+WxuhT+jn9sQXpQ2FFxZ8DMv/hjc= MIME-Version: 1.0 Received: by 10.229.237.129 with SMTP id ko1mr328149qcb.16.1311806656664; Wed, 27 Jul 2011 15:44:16 -0700 (PDT) Received: by 10.229.31.134 with HTTP; Wed, 27 Jul 2011 15:44:16 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 12:44:16 -1000 Message-ID: From: Tim Newsham To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Wed, 27 Jul 2011 23:03:36 +0000 Subject: Re: page fault in kernel X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 22:44:18 -0000 > So anyway, going to try a big overnight build to see if that has > completely resolved the issue or not. things are looking good so far. Looks like rearranging and reseating the ram addressed the problem. *phew* This is getting a little off topic, but any idea what might be wrong given how burnMMX is failing? Sounds like its at least not the primary cache. The fact that reseating or rearranging the RAM made it work makes me think that its not the secondary either. If it turns out that it happens only in specific RAM slots, then what would it most likely be? I ask because I'm wondering if replacing the CPU module would address the issue completely or if it might be something else on the motherboard. -- Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com