On Sat, 17 Feb 2018 13:00:23 +0000 Anne Wilson <cannewilson(a)googlemail.com&gt; wrote: here (after sleep mode, IINM): Feb 16 14:22:23 aw17 mcelog[2246]: Hardware event. This is not a software error. Feb 16 14:22:23 aw17 mcelog[2246]: MCE 0 Feb 16 14:22:23 aw17 mcelog[2246]: CPU 0 BANK 5 Feb 16 14:22:23 aw17 mcelog[2246]: MISC 38a0000086 ADDR ffb01fc0 Feb 16 14:22:23 aw17 mcelog[2246]: TIME 1518787341 Fri Feb 16 14:22:21 2018 Feb 16 14:22:23 aw17 mcelog[2246]: MCG status: Feb 16 14:22:23 aw17 mcelog[2246]: MCi status: Feb 16 14:22:23 aw17 mcelog[2246]: Uncorrected error Feb 16 14:22:23 aw17 mcelog[2246]: MCi_MISC register valid Feb 16 14:22:23 aw17 mcelog[2246]: MCi_ADDR register valid Feb 16 14:22:23 aw17 mcelog[2246]: Processor context corrupt Feb 16 14:22:23 aw17 mcelog[2246]: MCA: corrected filtering (some unreported errors in same region) Feb 16 14:22:23 aw17 mcelog[2246]: Generic CACHE Level-2 Generic Error Feb 16 14:22:23 aw17 mcelog[2246]: STATUS ae0000000040110a MCGSTATUS 0 Feb 16 14:22:23 aw17 mcelog[2246]: MCGCAP c09 APICID 0 SOCKETID 0 Feb 16 14:22:23 aw17 mcelog[2246]: CPUID Vendor Intel Family 6 Model 60 Do you see messages like the above? Try: journalctl -n 50000 I have errors along that line since 1.5 yrs or so, since I installed some Fedora the fist time on that machine. As long as no one tells me this is serious, and as long as I don't see smoke, fire, or sparks coming out of the computer, or hear strange noises from the machine: I won't care much. I'd start to care if hardware wasn't detected - things like that ... Regards -- Wolfgang Pfeiffer

On 18/2/18 7:45 pm, Tim wrote: Just following on from this, is my setup strange when I have never found boot.log to be empty and on my system it currently has mountains of entries? regards, Steve >

Allegedly, on or about 19 February 2018, Stephen Morris sent: Oops. The machine I'm working on now does have a boot.log, my prior ones didn't. It doesn't have the entire boot log though (everything that you see as the machine fires up). It starts logging part way through. The various kernel messages are not there. Many of the service ok/fail starts are in there. If I type in the "dmesg" command, that often starts off with the kind of info I see as the machine boots up (pre boot.log file contents), and ends with current kernel messages (such as info about recently plugged in USB devices). I appear to have a working /var/log/messages file, but don't recall doing anything to wrest that back from the modern binary journal that's supposed to replace it. -- [tim@localhost ~]$ uname -rsvp Linux 4.14.16-200.fc26.x86_64 #1 SMP Wed Jan 31 19:34:52 UTC 2018 x86_64 Boilerplate: All mail to my mailbox is automatically deleted. There is no point trying to privately email me, I only get to see the messages posted to the mailing list. Windows, it's enough to make a grown man cry!