panic in sys_fstatat (?)
Chris H
bsd-lists at bsdforge.com
Mon Feb 2 20:30:35 UTC 2015
On Mon, 2 Feb 2015 10:39:43 -0800 Steve Kargl
<sgk at 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 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current
mailing list