Comment 5 for bug 1789214

Revision history for this message
Joao Luis (jpluis) wrote :

Good evening!

I can give feedback right away from the last 2 notes.

The other workaround proposed (in askubuntu.com) of adding a kernel parameter intel_idle.max_cstate=1 seems to work well (max uptime tested is 6h 45min so far).

Regarding the indication to use 4.18.3-041803-generic, I downloaded and installed the packages (for my own record):

linux-headers-4.18.3-041803_4.18.3-041803.201808180530_all.deb
linux-headers-4.18.3-041803-generic_4.18.3-041803.201808180530_amd64.deb
linux-image-unsigned-4.18.3-041803-generic_4.18.3-041803.201808180530_amd64.deb
linux-modules-4.18.3-041803-generic_4.18.3-041803.201808180530_amd64.deb

The boot cmdline was:

root@jpsl-N8xxEL:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.18.3-041803-generic root=UUID=60daf8a6-ead0-4dc1-9b51-e7fa0fd7304c ro text
(
( Note that, it is without intel_idle.max_cstate=1 ) the kernel 4.18.3-041803-generic crashes / freezes frequently also. Already tested 3 times, so I added the tag kernel-bug-exists-upstream

(I should also mention that if I give the command "reboot" or "poweroff" using this kernel, it always freezes - but I don't know if this is related or not).