#1

$ sudo mcelog

mcelog: warning: 8 bytes ignored in each record
mcelog: consider an update

$ mcelog --is-cpu-supported

echo ?

0

$ head /proc/cpuinfo

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel® Core™ i7-8700K CPU @ 3.70GHz
stepping : 10
microcode : 0x96
cpu MHz : 800.239
cache size : 12288 KB
physical id : 0

$ cat /proc/version

Linux version 4.19.8-300.fc29.x86_64 (mockbuild@bkernel04.phx2.fedoraproject.org) (gcc version 8.2.1 20181105 (Red Hat 8.2.1-5) (GCC)) #1 SMP Mon Dec 10 15:23:11 UTC 2018

$ rpm -q mcelog

mcelog-153-3.fc29.x86_64

#2

Have you checked your CPU/RAM usage?

#3

Any errors in the journal? journalctl -b

#4

I apologize for the late reply, have been busy with work.

I have started to check the cpu/ram usage.

and there isn’t anything any errors currently in the journal.

#5

If you’ve got it installed, run memtest86 overnight. Random freezes often can be traced to either a few bad spots in RAM or power line fluctuations. There’s not much you can do about the power but you can swap out bad RAM. :wink:

#6

journalctl -b only shows the journal since the last successful reboot. If you had to reboot to clear the freeze, the error will be in the previous journal log, not the current one.

#7

Just in case it weren’t clear from this, journalctl -b-1 -e will show the logs from the last boot starting at the bottom.

Also, OP what GPU do you have? Would it happen to be NVIDIA?

#8

Just installed memtest86, and will be running it over night.

#9

Thank you that helps out.

This was one of the errors in the Journal.
systemd-coredump[3760]: Process 3757 (vulkandriverque) of user 1000 dumped core.Stack trace of thread 195:#0 0x00007fc0547e405f n/a (/usr/lib/x86_64-linux-gnu/libc-2.27.so)

I will be checking again once I encounter another freeze.

And I am running on my intel i7 8700k integrated GPU at the current moment. Have to wait a bit to get a decent GPU.

#10

There’s a way you can get a stack trace if the one in the journal isn’t useful. However, I’ve forgotten how to do it.

#11

Could you run coredumpctl debug vulkandriverque (you’ll need gdb or lldb installed), and then run bt to see a full stack trace of where the error occurred?

#12

it seems that problem was caused by me force terminating the Steam Flatpak.

So I am assuming that that was just a one time occurrence and not the cause.

I will keep you guys updated on anything else.

#13

Ran the Memtest86 all night and no problems were found. all the tests were passed with no errors.

#14

Just had a freeze and reboot.

Checked the journal.

mcelog[1037]: Hardware event. This is not a software error.
mcelog[1037]: MCE 0
mcelog[1037]: CPU 3 BANK 0 TSC 45db5c4f148
mcelog[1037]: ADDR 1ffffb729e2cf
mcelog[1037]: TIME 1550361592 Sat Feb 16 18:59:52 2019
mcelog[1037]: MCG status:
mcelog[1037]: MCi status:
mcelog[1037]: Corrected error
mcelog[1037]: Error enabled
mcelog[1037]: MCi_ADDR register valid
mcelog[1037]: MCA: Instruction CACHE Level-0 Instruction-Fetch Error
mcelog[1037]: STATUS 9400004000040150 MCGSTATUS 0
mcelog[1037]: MCGCAP c0c APICID 6 SOCKETID 0
mcelog[1037]: CPUID Vendor Intel Family 6 Model 158
mcelog[1037]: mcelog: warning: 8 bytes ignored in each record
mcelog[1037]: mcelog: consider an update
kernel: mce: [Hardware Error]: Machine check events logged

#15

What were you doing when this occurred? Most likely your CPU either overheating or is malfunctioning somehow.

#16

I was updating Flatpaks, I have been monitoring the temp and CPU. I haven’t seen any incremental changes.

#17

Just wanted to thank you all for you time and help.

One of the most recent updates has fixed the issue I was encountering.

1 Like