Once you've tested that it works, I recommend following this tutorial to automate it: ĮDIT: Forget compiling the kernel, just do the following:Īdd intel_idle. Sudo mkinitcpio -k 4.7.0-MANJARO -c /etc/nf -g /boot/initramfs-4.7.img (4.7.0-MANJARO is the kernel name kernel names are listed in /lib/modules) Make -j4 (change 4 to the # of cores you have) Make xconfig: Edit -> Find -> Type 'intel_idle' into the search bar and press Search -> Uncheck the box for the 'Cpuidle Driver for Intel Processors' -> Save -> Exit Make localyesconfig (if it asks you for any options, just hold enter to use defaults) tar.gz from here and run tar xvf and cd into the folder. You will need to reboot your server to apply the new configuration.Update your kernel to the latest version provided by your distro and ensure you're using open-source GPU driversĭownload a. Then please regenerated GRUB configuration: grub2-mkconfig -o /boot/grub2/grub.cfg In our evaluation, we focus on high performance sys-tems with Intel processors, using the intelidle driver. In order to do that, add intel_idle.max_cstate=1 entry to the kernel command line in /etc/default/grub.įor instance: GRUB_CMDLINE_LINUX='biosdevname=0 crashkernel=auto nomodeset rd.auto=1 consoleblank=0 intel_idle.max_cstate=1' The cpuidle governor implements the selection policy while the cpuidle driver implements the architecture-specic mecha-nism to request an idle state from the CPU 9. So basically we need to set up intel_idle module to use a simplified C-state logic. Similar problems are reported with different distributions. It can cause these issues when intel_idle driver doesn’t work properly with modern h/w C-states. This means that your CPU is likely using sophisticated C-state logic of modern CPUs. Intel(R) Core(TM) i9-9900K CPU 3.60GHz Released Changes Kernel 2.6.35 2010 Added intelidle (Intel CPUidle C-state driver) Kernel 2.6.36 2010 Added support for deep C-states in CPU offline.

You also use intel_idle driver on the server: # cat /sys/devices/system/cpu/cpuidle/current_driverĪmong the CPU models that we see having these problems more often are: It is possible that you will find these errors there: mce: : CPU 5: Machine Check Exception: 5 Bank 0: b200000000030005 If you see no apparent reason for this behavior, collect kdump report and check the corresponding vmcore-dmesg.txt file. Your server is frequently rebooted with 'Kernel panic - not synching' message (once per day or even more frequently).

Cpuidle Driver For Intel Processors