Sudden system reboots with Intel CPU [Hardware Error]

Support
1

Hi,

I am having the same 3 errors shown at this old thread on my new HP Z840 build.

Thanks,

Gerry

3

As it is a broadwell

( https://wiki.archlinux.org/title/Microcode#Loading_microcode )

I may be interested in your mkinitcpio.conf;

cat /etc/mkinitcpio.conf
4 
$ cat /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(usbhid xhci_hcd)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No RAID, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect modconf block filesystems fsck)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev modconf block filesystems fsck)
#
##   This setup assembles a mdadm array with an encrypted root file system.
##   Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
#    HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
##   This setup loads an lvm2 volume group.
#    HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
##   This will create a systemd based initramfs which loads an encrypted root filesystem.
#    HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr and fsck hooks.
HOOKS=(base udev autodetect kms modconf block keyboard keymap consolefont plymouth resume filesystems fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used for Linux ≥ 5.9 and gzip compression is used for Linux < 5.9.
# Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

# MODULES_DECOMPRESS
# Decompress loadable kernel modules and their firmware during initramfs
# creation. Switch (yes/no).
# Enable to allow further decreasing image size when using high compression
# (e.g. xz -9e or zstd --long --ultra -22) at the expense of increased RAM usage
# at early boot.
# Note that any compressed files will be placed in the uncompressed early CPIO
# to avoid double compression.
#MODULES_DECOMPRESS="no"
5

“This is mandatory for CPUs with severe hardware bugs, like the Intel Haswell and Broadwell processor families.”

What compatible processors would you recommend for my motherboard that are secure and stable?

Thanks again,

Gerry

6

Ok, I think we want to put microcode on that HOOKS line.

I dont know if you are familiar with editing system files.

But a simple approach would be using the micro editor and sudo;

sudo micro /etc/mkinitcpio.conf

Please edit the HOOKS line to include microcode and appear like so:

HOOKS=(base udev autodetect microcode kms modconf block keyboard keymap consolefont plymouth resume filesystems fsck)

Afterwards execute the following;

sudo mkinitcpio -P && sudo update-grub

After a reboot, well, I guess we will see if it still happens. :sweat_smile:


Most processors are compatible. That line refers to manufacturing/design flaws.

And generally hardware recommendations are discouraged.

It would make most sense simply to research processors in general … maybe compared to kernel support if considering something super brand new.

7

Thanks again for all your help. I will try this when I have a clear head. I have edited many system files to date.

IF I was to purchase the previous gen E5-2699 v3, would I have to do a clean install?

Thanks again,

Gerry

8

No worries, let us know.

According to the Arch snippet the Broadwell and Haswell lines are both considered to have ‘hardware bugs’ (the proposed processor is Haswell).

But I will also mention that in general if you were to swap in some intel processor in place of your current intel processor … you would likely have to do very little to accommodate it. You would want to rebuild initram and such, but package or config changes should largely not be needed excepting any particulars that could be discarded or edited - such as maybe some boot option you applied to workaround an issue created by the previous processor.

9

I see 6 HOOKS lines. Which one do I modify, 2 or 4 maybe?

 This setup specifies all modules in the MODULES setting above.
##   No RAID, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect modconf block filesystems fsck)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev modconf block filesystems fsck)
#
##   This setup assembles a mdadm array with an encrypted root file system.
##   Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
#    HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
##   This setup loads an lvm2 volume group.
#    HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
##   This will create a systemd based initramfs which loads an encrypted root filesystem.
#    HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck)
#
10

All of the ones you pasted here are commented.

That is they have # in front of them, making the line inactive.

The line to edit is the active, uncommented, one;

(This is taken from your original copy of the whole file. It should appear below all of the comments shared in your last post.)

11

I see it now. Only 4 real lines and all comments. I commented the old line. Does this auto-save on exit?

#    usr and fsck hooks.
##   HOOKS=(base udev autodetect kms modconf block keyboard keymap consolefont plymouth resume filesystems fsck)
HOOKS=(base udev autodetect microcode kms modconf block keyboard keymap consolefont plymouth resume filesystems fsck)

# COMPRESSION
12

A reasonable approach.

I’m not sure what you mean. If you opened it with an editor like micro or nano then it should prompt you if you try to exit without saving. You can of course save first using the key combo.
Ctrl+s for micro, Ctrl+x for nano, maybe different if using something else.

13

I am editing inside Terminal when running your script. Is it possible to save when editing inside terminal?

Got it, CTRL S. So much more to learn.

Gerry

14

typical for undervolting

15

I had thought it possibly related to ‘low powered’ cpu’s … but the model is considered power-hungry if anything.

But your comment reminds me that does not discount end user configuring a low-power state.

@mapman97 have you applied undervolting or similar?

16

Sorry guys, wouldn’t know how to do that. I was told this was a barely used small lab machine, so I left as is.

I did use the script below to change current policy to “ondemand” instead of schedutil. But, that was this morning. Looks like it’s running at 1.2.

sudo cpupower frequency-info

analyzing CPU 74:
  driver: intel_cpufreq
  CPUs which run at the same hardware frequency: 74
  CPUs which need to have their frequency coordinated by software: 74
  maximum transition latency: 20.0 us
  hardware limits: 1.20 GHz - 3.60 GHz
  available cpufreq governors: conservative ondemand userspace powersave performance schedutil
  current policy: frequency should be within 1.20 GHz and 3.60 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 1.20 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes

Gerry

17

do you have the optional 1200 watt power supply?

you must have the upgraded power supply, the stock 850 watt unit will not reliably boot/power the system when two 120 watt cpu’s are installed

19

Hi All,

I assume this is also an issue if I decide to convert to a Windows machine? I still have my very reliable Z820. Just need a better graphics card.

Thanks,

Gerry

20

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.