Infinite loop on Manjaro boot

Hi,
Since a few weeks my desktop computer started to have infinite loop when I am on the POST screen (This is a black screen where Manjaro is written at the bottom, 3 dots on top and the logo of my motherboard, a gigabyte Aorus) (I wanted to show you a photo that I took but the forum won’t let me upload it).

I suspect that this bug appeared after I used the suspend functionality too much, I think I know that this option in Linux desktop can cause bugs.

A temporary solution that I found:
I tried every kernel (the normal and its fallback initramfs version) on the boot menu of manjaro. After a couple of restarts and different kernels selection it boots normally. But the day after I keep being in the same issue. It doesn’t matter if the kernel is in a fallback version or not, after a certain number of tries it boots properly.

What I tried to solve the problem:
After booting up successfully with a kernel that does not bug, I tried in the terminal:

$ sudo mkinitcpio -P
$ sudo update-grub
$ sudo grub-install --efi-directory=/boot/efi

It does not solve the problem.

When an infinite loop appears before a successfull boot I get this journal errors:

$ journalctl -p3 -b-1
-- Journal begins at Wed 2021-01-20 10:01:00 CET, ends at Sat 2021-06-05 12:24:10 CEST. --
Jun 05 12:20:40 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:40 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:40 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:40 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:40 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro gnome-session-binary[934]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jun 05 12:21:00 manjaro systemd[1]: Failed to start Terminate Plymouth Boot Screen.
Jun 05 12:22:15 manjaro kernel: watchdog: watchdog0: watchdog did not stop!

Technical infos of my hardware and software:

$ inxi -F
    System:
      Host: manjaro Kernel: 5.12.2-1-MANJARO x86_64 bits: 64 
      Desktop: GNOME 3.38.4 Distro: Manjaro Linux 
    Machine:
      Type: Desktop System: Gigabyte product: B450 I AORUS PRO WIFI v: N/A 
      serial: <superuser required> 
      Mobo: Gigabyte model: B450 I AORUS PRO WIFI-CF v: x.x 
      serial: <superuser required> UEFI: American Megatrends v: F51 
      date: 07/29/2020 
    CPU:
      Info: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP cache: 
      L2: 4 MiB 
      Speed: 3593 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 3593 2: 2195 
      3: 2111 4: 2053 5: 2196 6: 2195 7: 2193 8: 2197 9: 2125 10: 2051 11: 2195 
      12: 2196 13: 2195 14: 2195 15: 3589 16: 2053 
    Graphics:
      Device-1: AMD Navi 14 [Radeon RX 5500/5500M / Pro 5500M] driver: amdgpu 
      v: kernel 
      Display: wayland server: X . org 1.20.11 driver: loaded: amdgpu 
      note: n/a (using device driver) - try sudo/root 
      resolution: <missing: xdpyinfo> 
      OpenGL: renderer: Radeon RX 5500 XT (NAVI14 DRM 3.40.0 5.12.2-1-MANJARO 
      LLVM 11.1.0) 
      v: 4.6 Mesa 21.0.3 
    Audio:
      Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel 
      Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel 
      Device-3: Razer USA Kraken Tournament Edition type: USB 
      driver: hid-generic,snd-usb-audio,usbhid 
      Sound Server-1: ALSA v: k5.12.2-1-MANJARO running: yes 
      Sound Server-2: PulseAudio v: 14.2 running: yes 
    Network:
      Device-1: Intel Wireless-AC 9260 driver: iwlwifi 
      IF: wlp7s0 state: down mac: 1e:68:f0:12:e6:71 
      Device-2: Intel I211 Gigabit Network driver: igb 
      IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: 18:c0:4d:2d:6e:d9 
      IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
    Bluetooth:
      Device-1: Intel Wireless-AC 9260 Bluetooth Adapter type: USB driver: btusb 
      Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running 
      rfk-block: hardware: no software: yes address: see --recommends 
    Drives:
      Local Storage: total: 912.89 GiB used: 363.78 GiB (39.8%) 
      ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP510 size: 447.13 GiB 
      ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
    Partition:
      ID-1: / size: 404.85 GiB used: 363.78 GiB (89.9%) fs: ext4 dev: /dev/dm-0 
      ID-2: /boot/efi size: 299.4 MiB used: 468 KiB (0.2%) fs: vfat 
      dev: /dev/nvme0n1p1 
    Swap:
      ID-1: swap-1 type: partition size: 34.51 GiB used: 0 KiB (0.0%) 
      dev: /dev/dm-1 
    Sensors:
      System Temperatures: cpu: 47.0 C mobo: 0 C gpu: amdgpu temp: 36.0 C 
      Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 
    Info:
      Processes: 401 Uptime: 1m Memory: 31.37 GiB used: 1.63 GiB (5.2%) 
      Shell: Zsh inxi: 3.3.04 

I have Manjaro on an Nvme and Windows 10 on an SSD. When I boot on windows 10 there is no problems.

I could reinstall Manjaro but I want to understand and fix the problem first if possible.
Thanks for your attention.

When you see Manjaro logo on the bottom you can press ESC key to see boot messages. Also upon a successful boot you can check logs of the previous unsuccessful one with journalctl -p3 -b-1

Hi,
Thanks for the tips.
When an ininite loop appears I can’t see boot messages when pressing ESC, there is still the loading dots moving but I can’t access any infos. The only action I can do is Ctrl Alt Del to reboot.

With the command journalctl -p3 -b-1, when no infinite loop appeared before the boot of the PC:

-- Journal begins at Wed 2021-01-20 10:01:00 CET, ends at Sat 2021-06-05 09:59:12 CEST. --
Jun 03 14:24:42 manjaro kernel: kvm: disabled by bios
Jun 03 14:24:42 manjaro kernel: kvm: disabled by bios
Jun 03 14:24:42 manjaro kernel: kvm: disabled by bios
Jun 03 14:24:42 manjaro kernel: kvm: disabled by bios
Jun 03 14:24:43 manjaro kernel: kvm: disabled by bios
Jun 03 14:24:43 manjaro kernel: kvm: disabled by bios
Jun 03 14:24:43 manjaro kernel: kvm: disabled by bios
Jun 03 14:24:43 manjaro kernel: kvm: disabled by bios
Jun 03 14:24:43 manjaro kernel: kvm: disabled by bios
Jun 03 14:24:43 manjaro kernel: kvm: disabled by bios
Jun 03 14:24:45 manjaro bluetoothd[829]: Failed to set mode: Blocked through rfkill (0x12)
Jun 03 14:25:32 manjaro gdm-password][2946]: gkr-pam: unable to locate daemon control file
Jun 03 14:25:34 manjaro systemd[2957]: Failed to start Application launched by gnome-session-binary.
Jun 03 21:48:35 manjaro pulseaudio[3160]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Jun 03 21:48:35 manjaro pulseaudio[3160]: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
Jun 03 21:48:35 manjaro pulseaudio[3160]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Jun 03 23:20:39 manjaro gnome-shell[3016]: Finalizing wrapper for an already freed object of type: St.Label
Jun 03 23:20:39 manjaro systemd-coredump[12411]: Failed to connect to coredump service: Connection refused
Jun 03 23:20:41 manjaro systemd-cryptsetup[13278]: Device luks-4fdc530d-7adb-4f32-8917-df8c5d5d3d88 is still in use.
Jun 03 23:20:41 manjaro systemd-cryptsetup[13278]: Failed to deactivate: Device or resource busy
Jun 03 23:20:41 manjaro systemd-cryptsetup[13286]: device-mapper: remove ioctl on luks-a1fd1530-5041-40e8-9bf6-c77622d6adee  failed: Device or resource busy

But with an infinite loop preceding a successful launch I have this:

-- Journal begins at Wed 2021-01-20 10:01:00 CET, ends at Sat 2021-06-05 12:24:10 CEST. --
Jun 05 12:20:40 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:40 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:40 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:40 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:40 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro kernel: kvm: disabled by bios
Jun 05 12:20:41 manjaro gnome-session-binary[934]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jun 05 12:21:00 manjaro systemd[1]: Failed to start Terminate Plymouth Boot Screen.
Jun 05 12:22:15 manjaro kernel: watchdog: watchdog0: watchdog did not stop!
  • I searched for KVM and it seems to be a Virtualization feature for AMD. Finally after some research, I found that KVM is related to SVM for the CPU in the BIOS. I enabled SVM feature in the BIOS and all KVM errors are gone. But the problem persists. After that, the journal looks like this:
manjaro gnome-session-binary[952]: Unrecoverable failure in required component org.gnome.Shell.desktop
manjaro systemd[1]: Failed to start Terminate Plymouth Boot Screen.
manjaro kernel: watchdog: watchdog0: watchdog did not stop!
  • During my research I think that the error:
    manjaro systemd[1]: Failed to start Terminate Plymouth Boot Screen.
    seems to be a more serious one. On the arch forum (bbs. archlinux. org/viewtopic.php?id=220900) I have found that someone had a mostly similar problem but the solution with the mkinitcpio command has already been tried on my part and failed.
  • For this error :
manjaro gnome-session-binary[952]: Unrecoverable failure in required component org.gnome.Shell.desktop

I have found a thread: bbs. archlinux. org/viewtopic.php?id=244029 where they say that it is not a critical error so I think it is not something that we should consider here.

Hi, a few updates back there was an issue with starting gdm not starting, this might have caught up with you if you missed some updates in between? link to stable update wiki post

GDM does not start (black screen when booting gnome edition)

Log into your system via tty and depending on your use of Plymouth or bootsplash-systemd choose a option from this post

Hi and thanks for the tips,
I installed updates via the TTY with those commands after logout:

$ sudo pacman -Syyuw 
$ sudo pacman -Syu 

Unfortunately, no updates to be done.

I then move on to the installation of plymouth but I have concerns about this. It seems according to the Arch Wiki (wiki. archlinux. org/title/Plymouth#Installation) that I need to modify something in the /etc/mkinitcpio.confdirectory. for the gdm-plymouth and libgdm-plymouthpackages to work? Is it possible to have the exact procedure because my drive is encrypted with LUKS.
Also, when I want to:

sudo pacman -S gdm-plymouth libgdm-plymouth

The terminal says that gdm-plymouth and gdm are in conflict, what should I do? If I have already gdm is better to keep it?

Strange Fact:
When I press ESC right after I boot into a kernel it seems to immediately go to the logon screen. It seems to be a temporary solution if I get tired of changing kernels.

Encrypted drive does not interfere I presume, do make sure you have backups when tinkering with your system. I’m not sure your issue is solved by one of these solutions but they are not difficult to try out and revert if they do not work.

Replacing gdm with gdm-plymouth worked for me. If you have terminal access you can also replace gdm-plymouth with gdm again, they are mutually exclusive: pamac info gdm-plymouth shows:

Name                  : gdm-plymouth
Description           : Display manager and login screen with plymouth support
Provides              : gdm
Conflicts With        : gdm

The other solution was to remove the splash kernel flag from /etc/default/grub and run

$ sudo update-grub