| 1 |
210924 Andrew Udvare wrote: |
| 2 |
> On 2021-09-24, at 05:58, Philip Webb <purslow@××××××××.net> wrote: |
| 3 |
>> While I was asleep yesterday, my machine reported on all 3 Konsoles : |
| 4 |
>> Message from syslogd@ at Thu Sep 23 19:38:11 2021 ... |
| 5 |
>> : mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: 9d0b4c16001d011b |
| 6 |
>> Message from syslogd@ at Thu Sep 23 19:38:11 2021 ... |
| 7 |
>> : mce: [Hardware Error]: TSC 0 ADDR 19e617980 MISC c01a000001000000 |
| 8 |
>> Message from syslogd@ at Thu Sep 23 19:38:11 2021 ... |
| 9 |
>> : mce: [Hardware Error]: PROCESSOR 2:600f20 TIME 1632440315 SOCKET 0 APIC 0 microcode 6000822 |
| 10 |
>> -- end of report -- |
| 11 |
> From the manpage: |
| 12 |
|
| 13 |
Which man page is that ? |
| 14 |
|
| 15 |
> Most errors can be corrected by the CPU |
| 16 |
> by internal error correction mechanisms. Uncorrected errors cause |
| 17 |
> machine check exceptions which may kill processes or panic the machine. |
| 18 |
> A small number of corrected errors is usually not a cause for worry, |
| 19 |
> but a large number can indicate future failure. |
| 20 |
|
| 21 |
So it looks as if the above was a correctable error. |
| 22 |
|
| 23 |
> When an uncorrected machine check error happens |
| 24 |
> that the kernel cannot recover from, then it will usually panic the system. |
| 25 |
> In this case when there was a warm reset after the panic, |
| 26 |
> mcelog should pick up the machine check errors after reboot. |
| 27 |
> This is not possible after a cold reset. |
| 28 |
|
| 29 |
No sign of any other effects : everything went on running. |
| 30 |
|
| 31 |
> If you are overclocking, try disabling it. |
| 32 |
|
| 33 |
No, I never overclock anything (smile). |
| 34 |
|
| 35 |
-- |
| 36 |
========================,,============================================ |
| 37 |
SUPPORT ___________//___, Philip Webb |
| 38 |
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto |
| 39 |
TRANSIT `-O----------O---' purslowatchassdotutorontodotca |
Archives