Date: Mon, 2 Feb 2015 10:39:43 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Eric van Gyzen <eric@vangyzen.net>, freebsd-current@freebsd.org Subject: Re: panic in sys_fstatat (?) Message-ID: <20150202183943.GA12198@troutmask.apl.washington.edu> In-Reply-To: <20150202182952.GR42409@kib.kiev.ua> References: <20150202175940.GA898@troutmask.apl.washington.edu> <54CFBDA7.8050309@vangyzen.net> <20150202182236.GA66843@troutmask.apl.washington.edu> <20150202182952.GR42409@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150202183943.GA12198>