Manjaro occasionally fails to wake from Cold Boot / Suspend

xashyar · 10 December 2020 20:50

I’ve been experiencing this for a long time, forcing me to force shutdown everytime ( Ctrl+Alt+F2 does not work) I also made Experiencing black blank screen on boot citing similar issues there as well.

sudo inxi -Fazy

Output

System:
  Kernel: 5.9.11-3-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.9-x86_64 
  root=UUID=73036dd4-76d9-492e-ab0f-055ca28fa40e rw pcie_aspm=off 
  intel_idle.max_cstate=1 quiet apparmor=1 security=apparmor 
  resume=UUID=866158db-e867-41da-b8af-91b73b6302cd 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: ASUSTeK product: N552VW v: 1.0 serial: <filter> 
  Mobo: ASUSTeK model: N552VW v: 1.0 serial: <filter> 
  UEFI: American Megatrends v: N552VW.304 date: 05/08/2019 
Battery:
  ID-1: BAT0 charge: 30.7 Wh condition: 35.5/47.5 Wh (75%) volts: 14.4/14.4 
  model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Discharging 
  cycles: 1391 
CPU:
  Info: Quad Core model: Intel Core i7-6700HQ socket: U3E1 bits: 64 
  type: MT MCP arch: Skylake-S family: 6 model-id: 5E (94) stepping: 3 
  microcode: E2 L1 cache: 256 KiB L2 cache: 6144 KiB L3 cache: 6000 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 41621 
  Speed: 900 MHz min/max: 800/3500 MHz base/boost: 3100/3500 volts: 1.1 V 
  ext-clock: 100 MHz Core speeds (MHz): 1: 869 2: 830 3: 845 4: 840 5: 889 
  6: 843 7: 840 8: 830 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  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: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable 
Graphics:
  Device-1: Intel HD Graphics 530 vendor: ASUSTeK driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:191b 
  Device-2: NVIDIA GM107M [GeForce GTX 960M] vendor: ASUSTeK driver: nouveau 
  v: kernel bus ID: 01:00.0 chip ID: 10de:139b 
  Device-3: Chicony HD WebCam (Asus N-series) type: USB driver: uvcvideo 
  bus ID: 1-4:3 chip ID: 04f2:b3fd serial: <filter> 
  Display: server: X.Org 1.20.10 driver: intel,nouveau unloaded: modesetting 
  alternate: fbdev,nv,vesa display ID: :0.0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") 
  s-diag: 583mm (23") 
  Monitor-1: HDMI2 res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.6") 
  diag: 551mm (21.7") 
  OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 20.2.3 
  direct render: Yes 
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:a170 
  Sound Server: ALSA v: k5.9.11-3-MANJARO 
Network:
  Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel port: e000 
  bus ID: 02:00.0 chip ID: 8086:095a 
  IF: wlp2s0 state: up mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK driver: r8169 v: kernel port: d000 bus ID: 03:00.1 
  chip ID: 10ec:8168 
  IF: enp3s0f1 state: down mac: <filter> 
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:
  Local Storage: total: 1.94 TiB used: 67.64 GiB (3.4%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda vendor: Samsung model: MZNLF128HCHP-00004 size: 119.24 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
  rev: 301Q scheme: GPT 
  ID-2: /dev/sdb vendor: Seagate model: ST2000LM003 HN-M201RAD size: 1.82 TiB 
  block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  rotation: 5400 rpm serial: <filter> rev: 0001 scheme: GPT 
Partition:
  ID-1: / raw size: 106.19 GiB size: 104.02 GiB (97.96%) 
  used: 67.64 GiB (65.0%) fs: ext4 block size: 4096 B dev: /dev/sda2 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 12.76 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/sda3 
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A gpu: nouveau temp: 30.0 C 
  Fan Speeds (RPM): cpu: 2100 
Info:
  Processes: 241 Uptime: 5m Memory: 11.60 GiB used: 1.69 GiB (14.6%) 
  Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: 1352 pacman: 1346 
  lib: 381 flatpak: 0 snap: 6 Shell: Bash (sudo) v: 5.0.18 
  running in: xfce4-terminal inxi: 3.1.08

I see some major errors in the journalctl output:

journalctl -xe -p3 -b-1

Output

 #1  0x00007f0876dabeac n/a (nouveau_dri.so + 0x4d2eac)
                                                #2  0x00007f0876dabda8 n/a (nouveau_dri.so + 0x4d2da8)
                                                #3  0x00007f0891b813e9 start_thread (libpthread.so.0 + 0x93e9)
                                                #4  0x00007f0891d92293 __clone (libc.so.6 + 0x100293)
░░ Subject: Process 812 (Xorg) dumped core
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░ 
░░ Process 812 (Xorg) crashed and dumped core.
░░ 
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Dec 10 05:37:53 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Dec 10 05:38:01 xashyar lightdm[1153]: gkr-pam: unable to locate daemon control file
Dec 10 05:38:05 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Dec 10 08:07:13 xashyar nm-openvpn[1591]: event_wait : Interrupted system call (code=4)
Dec 10 08:07:15 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
...skipping...
                                                #1  0x00007f0876dabeac n/a (nouveau_dri.so + 0x4d2eac)
                                                #2  0x00007f0876dabda8 n/a (nouveau_dri.so + 0x4d2da8)
                                                #3  0x00007f0891b813e9 start_thread (libpthread.so.0 + 0x93e9)
                                                #4  0x00007f0891d92293 __clone (libc.so.6 + 0x100293)
░░ Subject: Process 812 (Xorg) dumped core
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░ 
░░ Process 812 (Xorg) crashed and dumped core.
░░ 
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Dec 10 05:37:53 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Dec 10 05:38:01 xashyar lightdm[1153]: gkr-pam: unable to locate daemon control file
Dec 10 05:38:05 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Dec 10 08:07:13 xashyar nm-openvpn[1591]: event_wait : Interrupted system call (code=4)
Dec 10 08:07:15 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
...skipping...
                                                #1  0x00007f0876dabeac n/a (nouveau_dri.so + 0x4d2eac)
                                                #2  0x00007f0876dabda8 n/a (nouveau_dri.so + 0x4d2da8)
                                                #3  0x00007f0891b813e9 start_thread (libpthread.so.0 + 0x93e9)
                                                #4  0x00007f0891d92293 __clone (libc.so.6 + 0x100293)
░░ Subject: Process 812 (Xorg) dumped core
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░ 
░░ Process 812 (Xorg) crashed and dumped core.
░░ 
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Dec 10 05:37:53 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Dec 10 05:38:01 xashyar lightdm[1153]: gkr-pam: unable to locate daemon control file
Dec 10 05:38:05 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Dec 10 08:07:13 xashyar nm-openvpn[1591]: event_wait : Interrupted system call (code=4)
Dec 10 08:07:15 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
...skipping...
                                                #1  0x00007f0876dabeac n/a (nouveau_dri.so + 0x4d2eac)
                                                #2  0x00007f0876dabda8 n/a (nouveau_dri.so + 0x4d2da8)
                                                #3  0x00007f0891b813e9 start_thread (libpthread.so.0 + 0x93e9)
                                                #4  0x00007f0891d92293 __clone (libc.so.6 + 0x100293)
░░ Subject: Process 812 (Xorg) dumped core
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░ 
░░ Process 812 (Xorg) crashed and dumped core.
░░ 
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Dec 10 05:37:53 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Dec 10 05:38:01 xashyar lightdm[1153]: gkr-pam: unable to locate daemon control file
Dec 10 05:38:05 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]
Dec 10 08:07:13 xashyar nm-openvpn[1591]: event_wait : Interrupted system call (code=4)
Dec 10 08:07:15 xashyar kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ]

TriMoon · 10 December 2020 21:43

Just to rule out some possibilities:

How much RAM does your laptop have?
What is the output of: ls -la /dev/disk/by-uuid/866158db-e867-41da-b8af-91b73b6302cd
Did you check your hard disk for bad sectors?
Why did you need to use the pcie_aspm=off kernel parameter?

xashyar · 11 December 2020 03:29

  free

              total        used        free      shared  buff/cache   available
Mem:          11876        1965        8303         523        1606        9125
Swap:         13066           0       13066

lrwxrwxrwx 1 root root 10 Dec 11 05:57 /dev/disk/by-uuid/866158db-e867-41da-b8af-91b73b6302cd -> ../../sda3

I ran sudo badblocks -v a couple times and each time I got:

Pass completed, 0 bad blocks found. (0/0/0 errors)

It was suggested to me on the freezing issue I had earlier:

Which didn’t solve the issue, shall I remove it now?
I rarely experience the freeze issue…

TriMoon · 11 December 2020 07:00

Thank you for cooperating and providing the info

You used correct swap partition for resume in your kernel parameter.
The size of your swap is not less than your RAM. (RAM seems to be 12GiB, and swap is bigger.)
Can you run badblocks -v /dev/sda3 to be 100% sure that there are no badblocks in the space of the hardisk that your swap uses?
(Might be best to do these badblock tests, while booted from a LiveUSB)
Because pcie_aspm=off as kernel parameter was suggested to you and it didn’t make any difference, i don’t see any harm in removing it again.

So what is left to check now hmmm…

Maybe check the settings in your BIOS wrt Power management (APM), maybe you need to change some settings there, instead of the default values, and see if it helps.
While in the BIOS, you might also check the settings of your DRAM wrt the speed it is set to.
Because if your DRAM is used with a frequency it was not designed for, it might cause irregular memory corruptions.
Seeing you are using an Intel CPU with multiple graphics cards, you might try to add the kernel parameters add_efi_memmap intel_iommu=on and see if that helps in anyway. (I doubt it but you never know)

No idea what else to suggest at moment…

xashyar · 11 December 2020 15:56

I ran this for each sda1/sda2/sda3, every time returning Zero bad blocks.

There’s nothing related there to modify.

The same goes for RAM, it just shows the available RAM size, nothing I could find wrt frequency.

Sorry, I’m not really familiar, with this at which line should I add this?
Should I add it to etc/default/grub?

Thanks for your time…

TriMoon · 11 December 2020 15:59

At the same place, and same way, as where you have/had pcie_aspm=off

xashyar · 14 December 2020 20:43

Hello, @TriMoon

I just re-encountered the problem on Cold Boot, in spite of adding the parameters you suggested:

GRUB_CMDLINE_LINUX_DEFAULT="add_efi_memmap intel_iommu=on quiet apparmor=1 security=apparmor resume=UUID=866158db-e867-41da-b8af-91b73b6302cd udev.log

Edit: I had already removed pcie_aspm=off as well as intel_idle.max_cstate=1, I hope the latter’s omission wouldn’t change anything.

TriMoon · 15 December 2020 08:49

Well i don’t know what else to suggest and tbh im not very familiar with the options you mention to be able to say if they would affect anything.

Just out of curiosity:
Why did you use udev.log at end without any value?
Because AFAIK that controls the log level of the udev sub-system…

xashyar · 15 December 2020 19:48

Sorry it looks like I wasn’t able to see the line thoroughly in Terminal ( > sign at the end).

the actual value is:

udev.log_priority=3

Perhaps I should wait for the subsequent Kernel updates or perhaps a try a “clean reinstall”.