Re: 11-CURRENT r275641 panic: Unrecoverable machine check exception

2014-12-12 Thread Ivan Klymenko
This panic is reproduced as follows:
I'm trying to write *.iso an optical disc in k3b.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: 11-CURRENT r275641 panic: Unrecoverable machine check exception

2014-12-12 Thread Andriy Gapon
On 12/12/2014 21:46, Ivan Klymenko wrote:
> Hi.
> 
> 
> I see such a panic the first time in 10 years.

good

> Fri Dec 12 21:35:11 EET 2014
> 
> FreeBSD nonamehost.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r275641: Tue 
> Dec  9 17:03:43 EET 2014 
> ivan@nonamehost.local:/media/da0s1/obj/usr/src/sys/mk11  amd64
> 
> panic: Unrecoverable machine check exception

Google for "machine check exception" if you haven't yet.

-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: 11-CURRENT r275641 panic: Unrecoverable machine check exception

2014-12-13 Thread Ivan Klymenko
В Sat, 13 Dec 2014 02:18:47 +0200
Andriy Gapon  пишет:

> On 12/12/2014 21:46, Ivan Klymenko wrote:
> > Hi.
> > 
> > 
> > I see such a panic the first time in 10 years.
> 
> good

and how

> 
> > Fri Dec 12 21:35:11 EET 2014
> > 
> > FreeBSD nonamehost.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0
> > r275641: Tue Dec  9 17:03:43 EET 2014
> > ivan@nonamehost.local:/media/da0s1/obj/usr/src/sys/mk11  amd64
> > 
> > panic: Unrecoverable machine check exception
> 
> Google for "machine check exception" if you haven't yet.
> 

I very much doubt that it is a hardware problem - in the other case, I
would not write about it here

-CPU is not overclocked
-Memory (RAM) is in order
-no overheating
-panic accurately reproduced - not occur randomly
-Panic occurs without high load CPU
-mcelog --no-dmi --ascii - nothing


I suspect that the added non-existent instructions for my CPU

CPU: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz (2294.84-MHz K8-class CPU)
Origin="GenuineIntel"  Id=0x206a7  Family=0x6  Model=0x2a  Stepping=7
Dec 13 10:11:45 nonamehost kernel:
Features=0xbfebfbff
Features2=0x1fbae3bf
AMD Features=0x28100800
AMD Features2=0x1 Dec 13 10:11:45 nonamehost kernel:
XSAVE Features=0x1

and it manifests itself in the assembly source code with the flag
CPUTYPE?=corei7-avx

I certainly could be wrong - but how to know for sure the cause of the
panic?

Best regards.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 11-CURRENT r275641 panic: Unrecoverable machine check exception

2014-12-13 Thread Andriy Gapon
On 13/12/2014 11:38, Ivan Klymenko wrote:
> -mcelog --no-dmi --ascii - nothing

Really?
mcelog: Unsupported new Family 6 Model 2a CPU: only decoding architectural 
errors
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 1 BANK 6
MISC 30e386 ADDR bd8d4cc0
MCG status:RIPV MCIP
MCi status:
Error overflow
Uncorrected error
Error enabled
MCi_MISC register valid
MCi_ADDR register valid
Processor context corrupt
MCA: corrected filtering (some unreported errors in same region)
Data CACHE Level-2 Data-Read Error
STATUS fe241136 MCGSTATUS 5
MCGCAP c07 APICID 1 SOCKETID 0
CPUID Vendor Intel Family 6 Model 42

-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: 11-CURRENT r275641 panic: Unrecoverable machine check exception

2014-12-13 Thread Ivan Klymenko
В Sat, 13 Dec 2014 13:40:13 +0200
Andriy Gapon  пишет:

> On 13/12/2014 11:38, Ivan Klymenko wrote:
> > -mcelog --no-dmi --ascii - nothing
> 
> Really?
> mcelog: Unsupported new Family 6 Model 2a CPU: only decoding
> architectural errors HARDWARE ERROR. This is *NOT* a software problem!
> Please contact your hardware vendor
> CPU 1 BANK 6
> MISC 30e386 ADDR bd8d4cc0
> MCG status:RIPV MCIP
> MCi status:
> Error overflow
> Uncorrected error
> Error enabled
> MCi_MISC register valid
> MCi_ADDR register valid
> Processor context corrupt
> MCA: corrected filtering (some unreported errors in same region)
> Data CACHE Level-2 Data-Read Error
> STATUS fe241136 MCGSTATUS 5
> MCGCAP c07 APICID 1 SOCKETID 0
> CPUID Vendor Intel Family 6 Model 42
> 

hm. sorry
I was wrong file core.txt.xxx
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: 11-CURRENT r275641 panic: Unrecoverable machine check exception

2014-12-15 Thread Rang, Anton
> 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 0x30e386

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
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: 11-CURRENT r275641 panic: Unrecoverable machine check exception

2014-12-18 Thread Ivan Klymenko
В Mon, 15 Dec 2014 17:49:54 +
"Rang, Anton"  пишет:

> > 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 0x30e386
> 
> 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.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"