Do I have a strange power saving mode?

I have an issue with system freeze once in a while - like once or twice a month. It usually happens soon after system has resumed from hibernate. So I thought I should have a look in logs after an successful resume to see if there is something that could give a clue of why resume sometimes fail. So I ran:
dmesg -l emerg,alert,crit,err,warn
In the result I found:

[ 1404.361313] Uhhuh. NMI received for unknown reason 20 on CPU 0.
[ 1404.361314] Do you have a strange power saving mode enabled?
[ 1404.361315] Dazed and confused, but trying to continue

How would I know if I have a strange power saving mode enabled?

The rest of the dmseg output:

[ 1404.361313] Uhhuh. NMI received for unknown reason 20 on CPU 0.
[ 1404.361314] Do you have a strange power saving mode enabled?
[ 1404.361315] Dazed and confused, but trying to continue
[ 2143.060266] kauditd_printk_skb: 8 callbacks suppressed
[ 3683.060030] kauditd_printk_skb: 2 callbacks suppressed
[ 3698.060004] kauditd_printk_skb: 2 callbacks suppressed
[ 5567.057267] kauditd_printk_skb: 17 callbacks suppressed
[13869.004879] kauditd_printk_skb: 5 callbacks suppressed
[15862.695892] kauditd_printk_skb: 5 callbacks suppressed
[21472.938663] kauditd_printk_skb: 5 callbacks suppressed
[22698.156048] kauditd_printk_skb: 2 callbacks suppressed
[22723.018805] kauditd_printk_skb: 3 callbacks suppressed
[26695.792619] thermal thermal_zone4: failed to read out thermal zone (-61)
[26701.116054] kauditd_printk_skb: 3 callbacks suppressed
[32463.443724] kauditd_printk_skb: 3 callbacks suppressed
[38083.098906] kauditd_printk_skb: 2 callbacks suppressed
[42594.563622] queueing ieee80211 work while going to suspend
[42594.563622] queueing ieee80211 work while going to suspend
[42606.482364] kauditd_printk_skb: 2 callbacks suppressed
[42685.061331] SUPR0GipMap: fGetGipCpu=0x1b

inxi -Fazy

System:
  Kernel: 5.10.2-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 
  root=UUID=b71e4128-01e3-4565-97ec-2fa0745987aa rw apparmor=1 
  security=apparmor resume=UUID=daf0114f-9ff9-4f2e-884d-24924538c92b 
  udev.log_priority=3 
  Desktop: Xfce 4.14.3 tk: Gtk 3.24.23 info: xfce4-panel wm: xfwm4 
  dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Laptop System: SCHENKER product: SCHENKER_VIA_14_SVI14E20 v: N/A 
  serial: N/A Chassis: Notebook type: 10 serial: N/A 
  Mobo: SCHENKER model: L140CU serial: N/A UEFI: INSYDE v: 1.07.08 
  date: 03/27/2020 
Battery:
  ID-1: BAT0 charge: 54.5 Wh condition: 71.5/73.9 Wh (97%) volts: 8.4/7.7 
  model: Notebook BAT type: Li-ion serial: <filter> status: Charging 
CPU:
  Info: Quad Core model: Intel Core i5-10210U socket: BGA1528 (U3E1) 
  note: check bits: 64 type: MT MCP arch: Kaby Lake note: check family: 6 
  model-id: 8E (142) stepping: C (12) microcode: DE L2 cache: 6 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 33615 
  Speed: 1800 MHz min/max: 400/4200 MHz base/boost: 1485/8300 volts: 0.8 V 
  ext-clock: 100 MHz Core speeds (MHz): 1: 1800 2: 1800 3: 1800 4: 1800 
  5: 1800 6: 1800 7: 1800 8: 1800 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
  Type: srbds mitigation: TSX disabled 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel UHD Graphics vendor: CLEVO/KAPOK driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:9b41 
  Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo 
  bus ID: 1-7:2 chip ID: 04f2:b684 serial: <filter> 
  Display: x11 server: X.Org 1.20.10 driver: intel unloaded: modesetting 
  alternate: fbdev,vesa display ID: :0.0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
  s-diag: 582mm (22.9") 
  Monitor-1: eDP1 res: 1920x1080 hz: 60 dpi: 157 size: 310x170mm (12.2x6.7") 
  diag: 354mm (13.9") 
  OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.3.1 
  direct render: Yes 
Audio:
  Device-1: Intel vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel 
  alternate: snd_soc_skl,snd_sof_pci bus ID: 00:1f.3 chip ID: 8086:02c8 
  Sound Server: ALSA v: k5.10.2-2-MANJARO 
Network:
  Device-1: Intel Wireless-AC 9462 driver: iwlwifi v: kernel port: 3000 
  bus ID: 00:14.3 chip ID: 8086:02f0 
  IF: wlan0 state: up mac: <filter> 
  IF-ID-1: brfjt state: up speed: -1 duplex: unknown mac: <filter> 
  IF-ID-2: brmen state: up speed: 10000 Mbps duplex: unknown mac: <filter> 
  IF-ID-3: brptp state: up speed: 10000 Mbps duplex: unknown mac: <filter> 
  IF-ID-4: dumfjt state: unknown speed: N/A duplex: N/A mac: <filter> 
  IF-ID-5: dummen state: unknown speed: N/A duplex: N/A mac: <filter> 
  IF-ID-6: dumptp state: unknown speed: N/A duplex: N/A mac: <filter> 
  IF-ID-7: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
  IF-ID-8: veth2496eth0 state: up speed: 10000 Mbps duplex: full mac: <filter> 
  IF-ID-9: veth3422eth0 state: up speed: 10000 Mbps duplex: full mac: <filter> 
RAID:
  Device-1: m type: zfs status: ONLINE level: no-raid size: 476 GiB 
  free: 284 GiB allocated: 192 GiB 
  Components: Online: 
  1: nvme1n1 maj-min: 259:8 size: 476.94 GiB 
  Device-2: z type: zfs status: ONLINE level: no-raid size: 780 GiB 
  free: 246 GiB allocated: 534 GiB 
  Components: Online: 
  1: nvme0n1p7 maj-min: 259:7 size: 781.65 GiB 
Drives:
  Local Storage: total: raw: 1.38 TiB usable: 1.37 TiB 
  used: 290.28 GiB (20.6%) 
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SA2000M81000G 
  size: 931.51 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s 
  lanes: 4 serial: <filter> rev: S5Z42105 temp: 34.9 C 
  SMART: yes health: PASSED on: 29d 0h cycles: 382 
  read-units: 15,343,183 [7.85 TB] written-units: 9,572,968 [4.90 TB] 
  ID-2: /dev/nvme1n1 maj-min: 259:8 vendor: Micron model: 2200 MTFDHBA512TCK 
  size: 476.94 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s 
  lanes: 4 serial: <filter> rev: P1MU003 temp: 38.9 C 
  SMART: yes health: PASSED on: 27d 15h cycles: 976 
  read-units: 1,071,183 [548 GB] written-units: 1,092,006 [559 GB] 
Partition:
  ID-1: / raw size: 9.77 GiB size: 9.55 GiB (97.79%) used: 983.8 MiB (10.1%) 
  fs: ext4 block size: 4096 B dev: /dev/nvme0n1p3 maj-min: 259:3 
  ID-2: /boot/efi raw size: 300 MiB size: 299.4 MiB (99.80%) 
  used: 284 KiB (0.1%) fs: vfat block size: 512 B dev: /dev/nvme0n1p1 
  maj-min: 259:1 
  ID-3: /home raw size: 92.77 GiB size: 90.32 GiB (97.35%) 
  used: 12.74 GiB (14.1%) fs: ext4 block size: 4096 B dev: /dev/nvme0n1p6 
  maj-min: 259:6 
  ID-4: /usr raw size: 12.21 GiB size: 11.95 GiB (97.92%) 
  used: 8.94 GiB (74.8%) fs: ext4 block size: 4096 B dev: /dev/nvme0n1p5 
  maj-min: 259:5 
  ID-5: /var raw size: 9.28 GiB size: 9.07 GiB (97.78%) used: 1.94 GiB (21.4%) 
  fs: ext4 block size: 4096 B dev: /dev/nvme0n1p4 maj-min: 259:4 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 25.55 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/nvme0n1p2 maj-min: 259:2 
Sensors:
  System Temperatures: cpu: 43.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 470 Uptime: 1d 1h 56m wakeups: 30883 Memory: 23.22 GiB 
  used: 14.28 GiB (61.5%) Init: systemd v: 247 Compilers: gcc: 10.2.0 
  Packages: 1317 pacman: 1314 lib: 413 flatpak: 0 snap: 3 Shell: Bash (su) 
  v: 5.1.0 running in: xfce4-terminal inxi: 3.2.01 

Is there any reason that you haven’t run the recent stable update? 5.10 kernel has been updated.
Have you tried with 5.4 kernel?

When I go to add/remove software, and click on updates, I get the message that my system is up to date.

Edit: ran a database refresh. Then some updates appeared.
This issue (system freeze after resume) has be going on ever since I installed manjaro in september. I guess it was kernel 5.7 back then. I doubt the last bit of updates makes a huge difference to that issue. Maybe it will change the logged message after successful resume though.

The message did not show after the first hiber/resume after update/reboot. I’ll keep my eyes open if it returns after some usage.