From owner-freebsd-current@FreeBSD.ORG  Mon Feb  2 20:30:35 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 9DDC4D4B
 for <freebsd-current@freebsd.org>; Mon,  2 Feb 2015 20:30:35 +0000 (UTC)
Received: from udns.ultimatedns.net (unknown
 [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6EA0BE26
 for <freebsd-current@freebsd.org>; Mon,  2 Feb 2015 20:30:35 +0000 (UTC)
Received: from ultimatedns.net (localhost [127.0.0.1])
 by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t12KW1Ud019395;
 Mon, 2 Feb 2015 12:32:01 -0800 (PST)
 (envelope-from bsd-lists@bsdforge.com)
To: Konstantin Belousov <kostikbel@gmail.com>, Steve Kargl
 <sgk@troutmask.apl.washington.edu>
In-Reply-To: <20150202183943.GA12198@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>
From: "Chris H" <bsd-lists@bsdforge.com>
Subject: Re: panic in sys_fstatat (?)
Date: Mon, 02 Feb 2015 12:32:02 -0800
Content-Type: text/plain; charset=UTF-8; format=fixed
MIME-Version: 1.0
Message-id: <171bfc9d01d3315b35d5e10376550469@ultimatedns.net>
Content-Transfer-Encoding: 8bit
Cc: 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 20:30:35 -0000

On Mon, 2 Feb 2015 10:39:43 -0800 Steve Kargl
<sgk@troutmask.apl.washington.edu> wrote

> On Mon, Feb 02, 2015 at 08:29:52PM +0200, Konstantin Belousov wrote:
> > On Mon, Feb 02, 2015 at 10:22:36AM -0800, Steve Kargl wrote:
> > > (kgdb) f 6
> > > #6  0xffffffff80754567 in ufs_getattr (ap=<value optimized out>)
> > >     at /usr/src/sys/ufs/ufs/ufs_vnops.c:463
> > > 463                     vap->va_atime.tv_sec = ip->i_din2->di_atime;
> > > (kgdb) x/i $rip
> > > 0xffffffff80754567 <ufs_getattr+135>:   mov    0x20(%rax),%rax
> > > (kgdb) info reg
> > > rax            0xfefff80034ba0700       -72066389246343424
> > Note the single-bit error in the 0xf_e_fff8... address above.
> > Is this the same machine you reported the panic in pmap ?
> > 
> > May be, run memtest ?
> > 
> 
> 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. :)

--Chris
> 
> -- 
> Steve
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"