Date: Thu, 18 Dec 2014 23:31:17 +0200 From: Ivan Klymenko <fidaj@ukr.net> To: "Rang, Anton" <anton.rang@isilon.com> Cc: "freebsd-current@FreeBSD.org" <freebsd-current@FreeBSD.org>, Andriy Gapon <avg@FreeBSD.org> Subject: Re: 11-CURRENT r275641 panic: Unrecoverable machine check exception Message-ID: <20141218233117.045a8ed9@nonamehost.local> In-Reply-To: <F21EDC44C64DB34B90AF485AC3CEDD4B354B0A89@MX104CL01.corp.emc.com> References: <20141212214653.41cec479@nonamehost.local> <548B85E7.7000102@FreeBSD.org> <20141213113823.660a1e05@nonamehost.local> <F21EDC44C64DB34B90AF485AC3CEDD4B354B0A89@MX104CL01.corp.emc.com>
index | next in thread | previous in thread | raw e-mail
В Mon, 15 Dec 2014 17:49:54 +0000 "Rang, Anton" <anton.rang@isilon.com> пишет: > > I certainly could be wrong - but how to know for sure the cause of > > the panic? > > > MCA: CPU 0 UNCOR PCC OVER DCACHE L2 DRD error > > MCA: Address 0xbd8d4cc0 > > MCA: Misc 0x30e3000086 > > The "root cause" may be hard to determine, but the immediate cause > was helpfully decoded by the kernel. (Though I don't know whether all > of the model-specific fields were decoded.) > > UNCOR = uncorrected error > PCC = processor context corrupted (can't safely continue to execute, > thus the panic) OVER = error overflow (hmmm, multiple errors occurred) > DCACHE L2 DRD = data being read from L2 data cache > > The miscellaneous register indicates that 0xbd8d4cc0 is a physical > address. > > So this looks like a processor failure. If it is repeatable, though, > it may indicate either failed hardware or some problem in configuring > the processor (though I'm not sure how that could lead to a cache > error). > > Anton Thank you.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141218233117.045a8ed9>