< img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=177525256911397&ev=PageView&noscript=1" />

Hardware Error on Linux Debian GN31 J3710

delmuch

New Member
Hi everyone,

I installed a Debian 10 on a GN31. Since, I've every 5 minutes a hardware Error message like below
[15881.522618] mce: [Hardware Error]: TSC 0 ADDR 17411b260
[15881.522621] mce: [Hardware Error]: PROCESSOR 0:406c4 TIME 1611678669 SOCKET 0 APIC 0 microcode 410
[16192.790316] mce: [Hardware Error]: Machine check events logged
[16192.790333] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: 8400000000010151
[16192.804299] mce: [Hardware Error]: TSC 0 ADDR 316037f0
[16192.807588] mce: [Hardware Error]: PROCESSOR 0:406c4 TIME 1611678981 SOCKET 0 APIC 0 microcode 410
[16192.807615] mce: [Hardware Error]: Machine check events logged
[16192.810971] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 4: c400000000010151

Stress test doesn't change the frequency of those messages.
Have you an idea about the origin of this issue ?

Thanks,

Delmuch.
 

joey

Administrator
Staff member
This is a debian kernel problem, maybe you can try to go to the debian official website for help.
 

spikerguy

Member
Hi everyone,

I installed a Debian 10 on a GN31. Since, I've every 5 minutes a hardware Error message like below
[15881.522618] mce: [Hardware Error]: TSC 0 ADDR 17411b260
[15881.522621] mce: [Hardware Error]: PROCESSOR 0:406c4 TIME 1611678669 SOCKET 0 APIC 0 microcode 410
[16192.790316] mce: [Hardware Error]: Machine check events logged
[16192.790333] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: 8400000000010151
[16192.804299] mce: [Hardware Error]: TSC 0 ADDR 316037f0
[16192.807588] mce: [Hardware Error]: PROCESSOR 0:406c4 TIME 1611678981 SOCKET 0 APIC 0 microcode 410
[16192.807615] mce: [Hardware Error]: Machine check events logged
[16192.810971] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 4: c400000000010151

Stress test doesn't change the frequency of those messages.
Have you an idea about the origin of this issue ?

Thanks,

Delmuch.
Looks like a kernel issue.

Try to update the kernel or check in debian issue logs to see if you can find anything similar to this.

Try ubuntu for testing and see if the same error appears or not.

Most likely this should be fixed with kernel update. Looks like a regression of some sort.
 
Top Bottom