From owner-freebsd-current@FreeBSD.ORG  Mon Feb  2 21:12:05 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 40371C62
 for <freebsd-current@freebsd.org>; Mon,  2 Feb 2015 21:12:05 +0000 (UTC)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
 [128.95.76.21])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "troutmask", Issuer "troutmask" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 1A4DD3D5
 for <freebsd-current@freebsd.org>; Mon,  2 Feb 2015 21:12:05 +0000 (UTC)
Received: from troutmask.apl.washington.edu (localhost [127.0.0.1])
 by troutmask.apl.washington.edu (8.14.9/8.14.9) with ESMTP id t12LBwjO074416
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Mon, 2 Feb 2015 13:11:58 -0800 (PST)
 (envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
 by troutmask.apl.washington.edu (8.14.9/8.14.9/Submit) id t12LBwFL074415;
 Mon, 2 Feb 2015 13:11:58 -0800 (PST) (envelope-from sgk)
Date: Mon, 2 Feb 2015 13:11:58 -0800
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Chris H <bsd-lists@bsdforge.com>
Subject: Re: panic in sys_fstatat (?)
Message-ID: <20150202211158.GA1312@troutmask.apl.washington.edu>
References: <20150202175940.GA898@troutmask.apl.washington.edu>
 <54CFBDA7.8050309@vangyzen.net>
 <20150202182236.GA66843@troutmask.apl.washington.edu>
 <20150202182952.GR42409@kib.kiev.ua>
 <20150202183943.GA12198@troutmask.apl.washington.edu>
 <171bfc9d01d3315b35d5e10376550469@ultimatedns.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <171bfc9d01d3315b35d5e10376550469@ultimatedns.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: Konstantin Belousov <kostikbel@gmail.com>,
 Eric van Gyzen <eric@vangyzen.net>, freebsd-current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 21:12:05 -0000

On Mon, Feb 02, 2015 at 12:32:02PM -0800, Chris H wrote:
> On Mon, 2 Feb 2015 10:39:43 -0800 Steve Kargl
> > 
> > Yep, same hardware.  And, yes, I'm beginning to think it
> > is hardware as no one else is reporting a problem.
> > 
> > The system is less than 2 month old. :(   
> FWIW given the system is so young, you might want to
> consider BUS/CPU timing, or PSU (power supply) before
> giving up on the board/CPU/RAM.
> I had [apparent] CPU cache failures that ultimately turned
> out to be the PSU. So thought it worth mentioning. :)
> 

memtest86+ indicates that it is indeed a memory module.

Sorry about the seemingly bogus kernel panic emails.

-- 
Steve