From owner-freebsd-current@FreeBSD.ORG  Mon Feb  2 18:39:44 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 C267E134
 for <freebsd-current@freebsd.org>; Mon,  2 Feb 2015 18:39:44 +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 A0923F3A
 for <freebsd-current@freebsd.org>; Mon,  2 Feb 2015 18:39:44 +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 t12Idiw7066817
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Mon, 2 Feb 2015 10:39:44 -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 t12IdhWu066816;
 Mon, 2 Feb 2015 10:39:43 -0800 (PST) (envelope-from sgk)
Date: Mon, 2 Feb 2015 10:39:43 -0800
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Konstantin Belousov <kostikbel@gmail.com>
Subject: Re: panic in sys_fstatat (?)
Message-ID: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150202182952.GR42409@kib.kiev.ua>
User-Agent: Mutt/1.5.23 (2014-03-12)
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 18:39:44 -0000

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. :(   

-- 
Steve