Comments

1 Comments

The 4.14.11 update tripped a few machine checks immediately after booting (below), prior to asking for the password for the encrypted disk system. After entering the password the system booted without problem. The checks were recorded in dmesg and syslog after boot, but mcelog shows nothing, as it had not yet started.

Downgrading to 4.11.8-300, no machine checks were flagged. The system has been running well for years without machine checks. I don't know whether there is a real (latent?) hardware problem or if the Meltdown fixes are causing false errors.

This is an older system; info from /proc/cpuinfo follows.

model name : Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz stepping : 7 microcode : 0x70a

kernel: mce: [Hardware Error]: Machine check events logged kernel: mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 5: f200001010000e0f kernel: mce: [Hardware Error]: TSC 0 kernel: mce: [Hardware Error]: PROCESSOR 0:10677 TIME 1515699617 SOCKET 0 APIC 1 microcode 70a kernel: mce: [Hardware Error]: Machine check events logged kernel: mce: [Hardware Error]: CPU 2: Machine Check: 0 Bank 0: f200084000000800 kernel: mce: [Hardware Error]: TSC 0 kernel: mce: [Hardware Error]: PROCESSOR 0:10677 TIME 1515699617 SOCKET 0 APIC 2 microcode 70a kernel: mce: [Hardware Error]: CPU 2: Machine Check: 0 Bank 5: f200000034000e0f kernel: mce: [Hardware Error]: TSC 0 kernel: mce: [Hardware Error]: PROCESSOR 0:10677 TIME 1515699617 SOCKET 0 APIC 2 microcode 70a kernel: mce: [Hardware Error]: CPU 3: Machine Check: 0 Bank 5: f200000010000e0f kernel: mce: [Hardware Error]: TSC 0 kernel: mce: [Hardware Error]: PROCESSOR 0:10677 TIME 1515699617 SOCKET 0 APIC 3 microcode 70a