Date: Mon, 2 Feb 2015 13:11:58 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Chris H <bsd-lists@bsdforge.com> Cc: Konstantin Belousov <kostikbel@gmail.com>, Eric van Gyzen <eric@vangyzen.net>, freebsd-current@freebsd.org Subject: Re: panic in sys_fstatat (?) Message-ID: <20150202211158.GA1312@troutmask.apl.washington.edu> In-Reply-To: <171bfc9d01d3315b35d5e10376550469@ultimatedns.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150202211158.GA1312>