Stuck at loading initial ramdisk if update causes any changes to kernel/initcpios

fenglengshun · 20 September 2021 15:17

Hello, I'm not sure why, but if any update causes a change in kernel or otherwise causes a initcpios update, it'll get stuck at the "Loading linux-zen" and "Loading initial ramdisk" part.

Things that I have tried:

I have tried my other kernels, but the result are the same, even with the one lts kernel I kept.
I have tried updating everything but things that causes grub/initcpios/kernel updates, and they're fine.
I also have tried to uninstall vhba-module-dkms, the one extra dkms module I install, but even uninstalling that seems to result in the same issue.
I have tried to edit the boot option from grub, removing the splash option, but there was no change so I don't think it is another plymouth issue. My keyboard didn't even lit up, so I think the system really is stuck at initialiazing the ramdisk.

Recent system changes:

I recently tried out dnscrypt-proxy to get around Indonesian govt. censorship of Reddit, but it didn't work, so I removed it using sudo systemctl disable --now dnscrypt-proxy.socket and then sudo pacman -R dnscrypt-proxy. I only ever messed with its built-in config and enabled using socket method, so that should have reverted everything.
Recently did a sudo systemctl restart systemd-binfmt after seeing a message about it on update log, I think from doing a wine-tkg update.
Made virsh net-autostart default for NAT connection with VM.
Installed the following via pip to use with PixivUtil2: Pillow beautifulsoup4 demjson certifi mechanize PySocks colorama cloudscraper
Installed macast and syncplay, though I didn't do much with them.

Aside from the inxi, I have a log of the recent package changes and the exact upgrade log that creates the issues in the follow pastebin: Update log, Inxi pamac list - Pastebin.com

I'm pretty sure it's something I installed that's messing with the initcpios / grub config process but I'm not sure what. Maybe os-prober? In any case, I would appreciate any help anyone can give, thank you.

$ inxi -Faz

System:    Kernel: 5.14.2-zen1-2-zen x86_64 bits: 64 compiler: gcc v: 11.1.0  
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=e63fe665-d42b-482a-aaf3-0fff940dd352  
rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 2 dm: SDDM  
Distro: Garuda Linux base: Arch Linux  
Machine:   Type: Desktop Mobo: ASRock model: A320M-HDV R4.0 serial: <filter> UEFI: American Megatrends  
v: P2.30 date: 06/26/2019  
Battery:   Device-1: hidpp_battery_0 model: Logitech M585/M590 Multi-Device Mouse serial: <filter>  
charge: 55% (should be ignored) rechargeable: yes status: Discharging  
CPU:       Info: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP  
arch: Zen family: 17 (23) model-id: 18 (24) stepping: 1 microcode: 8108102 cache: L2: 2 MiB  
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59200  
Speed: 3463 MHz min/max: N/A Core speeds (MHz): 1: 3463 2: 3700 3: 3700 4: 3700 5: 3700 6: 3700  
7: 3700 8: 3700  
Vulnerabilities: Type: itlb_multihit status: Not affected  
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: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling  
Type: srbds status: Not affected  
Type: tsx_async_abort status: Not affected  
Graphics:  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: Tul driver: amdgpu  
v: kernel bus-ID: 01:00.0 chip-ID: 1002:67df class-ID: 0300  
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: amdgpu,ati  
unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1  
Screen-1: 0 s-res: 3286x1080 s-dpi: 96 s-size: 869x285mm (34.2x11.2") s-diag: 915mm (36")  
Monitor-1: DisplayPort-2 res: 1920x1080 hz: 60 dpi: 30 size: 1600x900mm (63.0x35.4")  
diag: 1836mm (72.3")  
Monitor-2: HDMI-A-0 res: 1366x768 hz: 60 dpi: 101 size: 344x193mm (13.5x7.6")  
diag: 394mm (15.5")  
OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.42.0 5.14.2-zen1-2-zen LLVM 12.0.1)  
v: 4.6 Mesa 21.2.1 direct render: Yes  
Audio:     Device-1: AMD Family 17h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel  
bus-ID: 07:00.6 chip-ID: 1022:15e3 class-ID: 0403  
Sound Server-1: ALSA v: k5.14.2-zen1-2-zen running: yes  
Sound Server-2: JACK v: 1.9.19 running: no  
Sound Server-3: PulseAudio v: 15.0 running: yes  
Sound Server-4: PipeWire v: 0.3.35 running: yes  
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169  
v: kernel port: e000 bus-ID: 06:00.0 chip-ID: 10ec:8168 class-ID: 0200  
IF: enp6s0 state: down mac: <filter>  
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus-ID: 1-4:2  
chip-ID: 148f:7601 class-ID: 0000 serial: <filter>  
IF: wlp2s0f0u4 state: up mac: <filter>  
IF-ID-1: anbox0 state: down mac: <filter>  
Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-9:4 chip-ID: 0cf3:e009  
class-ID: e001  
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>  
Drives:    Local Storage: total: 5.68 TiB used: 2.3 TiB (40.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000VM002-1CT162 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5900
serial: <filter> rev: SC23 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD40EZRX-00SPEB0 size: 3.64 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400
serial: <filter> rev: 0A80 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WDS240G2G0B-00EPW0 size: 223.58 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0000
scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Seagate model: Expansion size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 060E scheme: GPT
Partition: ID-1: / raw-size: 223.32 GiB size: 223.32 GiB (100.00%) used: 39.68 GiB (17.8%) fs: btrfs
dev: /dev/sdc2 maj-min: 8:34
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%) used: 562 KiB (0.2%) fs: vfat
dev: /dev/sdc1 maj-min: 8:33
ID-3: /home raw-size: 223.32 GiB size: 223.32 GiB (100.00%) used: 39.68 GiB (17.8%) fs: btrfs
dev: /dev/sdc2 maj-min: 8:34
ID-4: /var/log raw-size: 223.32 GiB size: 223.32 GiB (100.00%) used: 39.68 GiB (17.8%)
fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-5: /var/tmp raw-size: 223.32 GiB size: 223.32 GiB (100.00%) used: 39.68 GiB (17.8%)
fs: btrfs dev: /dev/sdc2 maj-min: 8:34
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.28 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 61.6 C mobo: N/A gpu: amdgpu temp: 71.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 338
Info:      Processes: 402 Uptime: 15m wakeups: 10 Memory: 31.28 GiB used: 6.69 GiB (21.4%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: 1804 pacman: 1775
lib: 537 flatpak: 29 snap: 0 Shell: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06

jonathon · 21 September 2021 01:31

Interesting. I guess I'd start by checking if there's an /etc/mkinitcpio.conf.pacnew that needs to be merged, then see what the output of mkinitpcio -p linux-zen says.

fenglengshun · 21 September 2021 04:08

I don't see any /etc/mkinitcpio.conf.pacnew on my side. Is it possible to dry run mkinitpcio? I'd have to prepare another restore point and wait until tomorrow for some free time, otherwise.

jonathon · 21 September 2021 14:04

mkinitcpio by itself won’t write anything to disk. You can increase the verbosity of output with mkinitcpio -v .

fenglengshun · 21 September 2021 15:53

Here are the outputs:

$ mkinitcpio -p linux-zen

==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
  ==> ERROR: Unable to write to /boot/initramfs-linux-zen.img
==> ERROR: Unable to write to /boot/initramfs-linux-zen-fallback.img


$ mkinitcpio

==> Starting dry run: 5.14.2-zen1-2-zen
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Dry run complete, use -g IMAGE to generate a real image
==> WARNING: Possibly missing firmware for module: xhci_pci

(copy pasted the warning/error at the end that wasn't piped to the log file)

Verbose output on pastebin.

jonathon · 21 September 2021 15:58

This looks like a problem.

Where is your /boot directory located (does it have free space?). Can you check on the file permissions within it, e.g.

ls -al /boot

fenglengshun · 21 September 2021 17:04

ls -al /boot
total 317169
drwxr-xr-x 1 root root      528 Sep 13 19:08 .
drwxr-xr-x 1 root root      224 Sep 12 18:27 ..
-rw-r--r-- 1 root root    40960 Aug 18 18:21 amd-ucode.img
drwx------ 3 root root      512 Jan  1  1970 efi
drwxr-xr-x 1 root root      112 Sep 13 19:08 grub
-rw-r--r-- 1 root root 54719792 Sep 16 22:00 initramfs-linux-lts-fallback.img
-rw-r--r-- 1 root root 35193494 Sep 16 22:00 initramfs-linux-lts.img
-rw-r--r-- 1 root root 63169214 Sep 16 22:00 initramfs-linux-tkg-muqss-fallback.img
-rw-r--r-- 1 root root 38399845 Sep 16 22:00 initramfs-linux-tkg-muqss.img
-rw-r--r-- 1 root root 64574068 Sep 16 22:00 initramfs-linux-zen-fallback.img
-rw-r--r-- 1 root root 39213365 Sep 16 22:00 initramfs-linux-zen.img
drwxr-xr-x 1 root root       22 Aug  9 17:55 memtest86+
-rw-r--r-- 1 root root  9318400 Sep 13 19:08 vmlinuz-linux-lts
-rw-r--r-- 1 root root  9657504 Sep 12 16:19 vmlinuz-linux-tkg-muqss
-rw-r--r-- 1 root root 10476768 Sep 12 15:38 vmlinuz-linux-zen

Note, I was running mkinitcpio as a normal user (no sudo) for that dry run.

/boot

Partitions:

Also my Garuda Boot Options, if that matters:

quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3

jonathon · 21 September 2021 19:41

Well… that would explain why it couldn’t write the file, then…

I can’t see anything obviously wrong in any of the output.

Could you upload your /etc/mkinitcpio.conf somewhere?

fenglengshun · 22 September 2021 12:27

Yeah, wasn’t keen on running with sudo since I’m not familiar with mkinitcpio - at least not without some free time just in case (like on weekends).

Here: https://pastebin.com/mJaFmkTy

jonathon · 22 September 2021 12:37

OK, that looks like an older-format file.

Let's try using the default:

github.com

archlinux/mkinitcpio/blob/master/mkinitcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

This file has been truncated. show original

Grab a copy of that config file, then use it to generate an initramfs for one kernel and see if it helps:

sudo mkinitcpio -p linux-lts -C default-mkinitcpio.conf

If it does, then reintroduce changes one at a time to find out which one causes the issue.

fenglengshun · 22 September 2021 15:18

It doesn't work - not sure why myself.

Tried it on its own, then I checked if I could just upgrade linux-lts and then do the mkinitcpio from linux-zen but it also doesn't work, and just in case I also tried to both remove then reinstall linux-lts as well as try linux-lts-tkg-cacule which I have never installed so it shouldn't have any previous configs.

I have the logs here: mkinitcpio linux-lts test - Pastebin.com

(didn't have the log for the reinstall and install cacule part, just immediately hit restart without pasting it to the pastebin first)

jonathon · 22 September 2021 16:40

Grr... the preset file is overriding the default-mkinitcpio.conf...

$ sudo mkinitcpio -p linux-lts -c default-mkinitcpio.conf
[sudo] password for fenglengshun:           
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
-> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img

So, let's try

sudo mkinitcpio -k /boot/vmlinuz-linux-lts -c default-mkinitcpio.conf -g /boot/initramfs-linux-lts.img

and see if that makes a difference.

fenglengshun · 22 September 2021 23:44

[sudo] password for fenglengshun:
/usr/bin/mkinitcpio: line 483: default-mkinitcpio.conf: No such file or directory
==> ERROR: Failed to read configuration `default-mkinitcpio.conf'

...I don't think that's normal or expected?

jonathon · 22 September 2021 23:47

Did you download the file I linked to and name it default-mkinitcpio.conf ? If not, do so, then make sure you're giving the correct path to the file. I can't know where you will save the file so you'll have to work that one out yourself.

fenglengshun · 22 September 2021 23:56

Oh, right, I just used the file on my normal /etc/mkinitcpio. So just in case I made a new file now:

sudo mkinitcpio -k /boot/vmlinuz-linux-lts -c /etc/default-mkinitcpio.conf -g /boot/initramfs-linux-lts.i
mg
[sudo] password for fenglengshun:
==> Starting build: 5.10.67-1-lts
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts.img
==> Image generation successfu

It still doesn't boot. Maybe it's the zstd-compression?

jonathon · 22 September 2021 23:59

OK, so let's check the journal for the failed boot.

journalctl -b-1

will display the journal from the previous ("-1"st) boot. If it doesn't get to that point then there's just something odd happening.

fenglengshun · 23 September 2021 00:18

$ journalctl -b-1

-- Journal begins at Sun 2021-09-12 14:04:11 WIB, ends at Thu 2021-09-23 07:00:02 WIB. --
Sep 23 06:36:47 Garuda-PC kernel: Linux version 5.14.2-zen1-2-zen (linux-zen@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 ZEN SMP PREEMPT Thu, 09 Sep 2021 09:42:32 +0000
Sep 23 06:36:47 Garuda-PC kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=e63fe665-d42b-482a-aaf3-0fff940dd352 rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3
Sep 23 06:36:47 Garuda-PC kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Sep 23 06:36:47 Garuda-PC kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Sep 23 06:36:47 Garuda-PC kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Sep 23 06:36:47 Garuda-PC kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Sep 23 06:36:47 Garuda-PC kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Sep 23 06:36:47 Garuda-PC kernel: signal: max sigframe size: 1776
Sep 23 06:36:47 Garuda-PC kernel: BIOS-provided physical RAM map:
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009cfffff] usable
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x0000000009d00000-0x0000000009ffffff] reserved
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20afff] ACPI NVS
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x000000000a20b000-0x000000000affffff] usable
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000da465fff] usable
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x00000000da466000-0x00000000db944fff] reserved
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x00000000db945000-0x00000000dbac4fff] usable
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x00000000dbac5000-0x00000000dbed3fff] ACPI NVS
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x00000000dbed4000-0x00000000dcc45fff] reserved
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x00000000dcc46000-0x00000000dccd6fff] type 20
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x00000000dccd7000-0x00000000deffffff] usable
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000ffffffff] reserved
Sep 23 06:36:47 Garuda-PC kernel: BIOS-e820: [mem 0x0000000100000000-0x000000081f33ffff] usable
Sep 23 06:36:47 Garuda-PC kernel: NX (Execute Disable) protection: active
Sep 23 06:36:47 Garuda-PC kernel: efi: EFI v2.70 by American Megatrends
Sep 23 06:36:47 Garuda-PC kernel: efi: ACPI 2.0=0xdbe50000 ACPI=0xdbe50000 SMBIOS=0xdcb0b000 SMBIOS 3.0=0xdcb0a000 MEMATTR=0xd8eb3018 ESRT=0xd92d3198 
Sep 23 06:36:47 Garuda-PC kernel: SMBIOS 3.2.1 present.
Sep 23 06:36:47 Garuda-PC kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./A320M-HDV R4.0, BIOS P2.30 06/26/2019
Sep 23 06:36:47 Garuda-PC kernel: tsc: Fast TSC calibration using PIT
Sep 23 06:36:47 Garuda-PC kernel: tsc: Detected 3700.301 MHz processor
Sep 23 06:36:47 Garuda-PC kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 23 06:36:47 Garuda-PC kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 23 06:36:47 Garuda-PC kernel: last_pfn = 0x81f340 max_arch_pfn = 0x400000000
Sep 23 06:36:47 Garuda-PC kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Sep 23 06:36:47 Garuda-PC kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
Sep 23 06:36:47 Garuda-PC kernel: last_pfn = 0xdf000 max_arch_pfn = 0x400000000
Sep 23 06:36:47 Garuda-PC kernel: esrt: Reserving ESRT space from 0x00000000d92d3198 to 0x00000000d92d31d0.
Sep 23 06:36:47 Garuda-PC kernel: e820: update [mem 0xd92d3000-0xd92d3fff] usable ==> reserved
Sep 23 06:36:47 Garuda-PC kernel: Using GB pages for direct mapping
Sep 23 06:36:47 Garuda-PC kernel: Secure boot disabled
Sep 23 06:36:47 Garuda-PC kernel: RAMDISK: [mem 0x3350f000-0x35a7efff]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Early table checksum verification disabled
Sep 23 06:36:47 Garuda-PC kernel: ACPI: RSDP 0x00000000DBE50000 000024 (v02 ALASKA)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: XSDT 0x00000000DBE50098 0000B4 (v01 ALASKA A M I    01072009 AMI  00010013)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: FACP 0x00000000DBE56A88 000114 (v06 ALASKA A M I    01072009 AMI  00010013)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: DSDT 0x00000000DBE501E8 00689F (v02 ALASKA A M I    01072009 INTL 20120913)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: FACS 0x00000000DBEBCE00 000040
Sep 23 06:36:47 Garuda-PC kernel: ACPI: APIC 0x00000000DBE56BA0 00015E (v03 ALASKA A M I    01072009 AMI  00010013)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: FPDT 0x00000000DBE56D00 000044 (v01 ALASKA A M I    01072009 AMI  00010013)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: FIDT 0x00000000DBE56D48 00009C (v01 ALASKA A M I    01072009 AMI  00010013)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: SSDT 0x00000000DBE56DE8 000094 (v02 ALASKA CPUSSDT  01072009 AMI  01072009)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: SSDT 0x00000000DBE56E80 005419 (v02 AMD    AmdTable 00000002 MSFT 02000002)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: SSDT 0x00000000DBE5C2A0 00307E (v01 AMD    AMD AOD  00000001 INTL 20120913)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: MCFG 0x00000000DBE5F320 00003C (v01 ALASKA A M I    01072009 MSFT 00010013)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: AAFT 0x00000000DBE5F360 0003EA (v01 ALASKA OEMAAFT  01072009 MSFT 00000097)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: HPET 0x00000000DBE5F750 000038 (v01 ALASKA A M I    01072009 AMI  00000005)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: UEFI 0x00000000DBE5F788 000042 (v01 ALASKA A M I    00000002      01000013)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: BGRT 0x00000000DBE5F7D0 000038 (v01 ALASKA A M I    01072009 AMI  00010013)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: IVRS 0x00000000DBE5F808 0000D0 (v02 AMD    AMD IVRS 00000001 AMD  00000000)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: CRAT 0x00000000DBE5F8D8 000810 (v01 AMD    AMD CRAT 00000001 AMD  00000001)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: CDIT 0x00000000DBE600E8 000029 (v01 AMD    AMD CDIT 00000001 AMD  00000001)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: SSDT 0x00000000DBE60118 001D4A (v01 AMD    AmdTable 00000001 INTL 20120913)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: SSDT 0x00000000DBE61E68 0000BF (v01 AMD    AMD PT   00001000 INTL 20120913)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: WSMT 0x00000000DBE61F28 000028 (v01 ALASKA A M I    01072009 AMI  00010013)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving FACP table memory at [mem 0xdbe56a88-0xdbe56b9b]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving DSDT table memory at [mem 0xdbe501e8-0xdbe56a86]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving FACS table memory at [mem 0xdbebce00-0xdbebce3f]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving APIC table memory at [mem 0xdbe56ba0-0xdbe56cfd]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving FPDT table memory at [mem 0xdbe56d00-0xdbe56d43]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving FIDT table memory at [mem 0xdbe56d48-0xdbe56de3]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving SSDT table memory at [mem 0xdbe56de8-0xdbe56e7b]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving SSDT table memory at [mem 0xdbe56e80-0xdbe5c298]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving SSDT table memory at [mem 0xdbe5c2a0-0xdbe5f31d]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving MCFG table memory at [mem 0xdbe5f320-0xdbe5f35b]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving AAFT table memory at [mem 0xdbe5f360-0xdbe5f749]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving HPET table memory at [mem 0xdbe5f750-0xdbe5f787]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving UEFI table memory at [mem 0xdbe5f788-0xdbe5f7c9]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving BGRT table memory at [mem 0xdbe5f7d0-0xdbe5f807]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving IVRS table memory at [mem 0xdbe5f808-0xdbe5f8d7]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving CRAT table memory at [mem 0xdbe5f8d8-0xdbe600e7]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving CDIT table memory at [mem 0xdbe600e8-0xdbe60110]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving SSDT table memory at [mem 0xdbe60118-0xdbe61e61]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving SSDT table memory at [mem 0xdbe61e68-0xdbe61f26]
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Reserving WSMT table memory at [mem 0xdbe61f28-0xdbe61f4f]
Sep 23 06:36:47 Garuda-PC kernel: No NUMA configuration found
Sep 23 06:36:47 Garuda-PC kernel: Faking a node at [mem 0x0000000000000000-0x000000081f33ffff]
Sep 23 06:36:47 Garuda-PC kernel: NODE_DATA(0) allocated [mem 0x81f33c000-0x81f33ffff]
Sep 23 06:36:47 Garuda-PC kernel: Zone ranges:
Sep 23 06:36:47 Garuda-PC kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Sep 23 06:36:47 Garuda-PC kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Sep 23 06:36:47 Garuda-PC kernel:   Normal   [mem 0x0000000100000000-0x000000081f33ffff]
Sep 23 06:36:47 Garuda-PC kernel:   Device   empty
Sep 23 06:36:47 Garuda-PC kernel: Movable zone start for each node
Sep 23 06:36:47 Garuda-PC kernel: Early memory node ranges
Sep 23 06:36:47 Garuda-PC kernel:   node   0: [mem 0x0000000000001000-0x000000000009ffff]
Sep 23 06:36:47 Garuda-PC kernel:   node   0: [mem 0x0000000000100000-0x0000000009cfffff]
Sep 23 06:36:47 Garuda-PC kernel:   node   0: [mem 0x000000000a000000-0x000000000a1fffff]
Sep 23 06:36:47 Garuda-PC kernel:   node   0: [mem 0x000000000a20b000-0x000000000affffff]
Sep 23 06:36:47 Garuda-PC kernel:   node   0: [mem 0x000000000b020000-0x00000000da465fff]
Sep 23 06:36:47 Garuda-PC kernel:   node   0: [mem 0x00000000db945000-0x00000000dbac4fff]
Sep 23 06:36:47 Garuda-PC kernel:   node   0: [mem 0x00000000dccd7000-0x00000000deffffff]
Sep 23 06:36:47 Garuda-PC kernel:   node   0: [mem 0x0000000100000000-0x000000081f33ffff]
Sep 23 06:36:47 Garuda-PC kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000081f33ffff]
Sep 23 06:36:47 Garuda-PC kernel: On node 0, zone DMA: 1 pages in unavailable ranges
Sep 23 06:36:47 Garuda-PC kernel: On node 0, zone DMA: 96 pages in unavailable ranges
Sep 23 06:36:47 Garuda-PC kernel: On node 0, zone DMA32: 768 pages in unavailable ranges
Sep 23 06:36:47 Garuda-PC kernel: On node 0, zone DMA32: 11 pages in unavailable ranges
Sep 23 06:36:47 Garuda-PC kernel: On node 0, zone DMA32: 32 pages in unavailable ranges
Sep 23 06:36:47 Garuda-PC kernel: On node 0, zone DMA32: 5343 pages in unavailable ranges
Sep 23 06:36:47 Garuda-PC kernel: On node 0, zone DMA32: 4626 pages in unavailable ranges
Sep 23 06:36:47 Garuda-PC kernel: On node 0, zone Normal: 4096 pages in unavailable ranges
Sep 23 06:36:47 Garuda-PC kernel: On node 0, zone Normal: 3264 pages in unavailable ranges
Sep 23 06:36:47 Garuda-PC kernel: ACPI: PM-Timer IO Port: 0x808
Sep 23 06:36:47 Garuda-PC kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Sep 23 06:36:47 Garuda-PC kernel: IOAPIC[0]: apic_id 9, version 33, address 0xfec00000, GSI 0-23
Sep 23 06:36:47 Garuda-PC kernel: IOAPIC[1]: apic_id 10, version 33, address 0xfec01000, GSI 24-55
Sep 23 06:36:47 Garuda-PC kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
Sep 23 06:36:47 Garuda-PC kernel: ACPI: Using ACPI (MADT) for SMP configuration information
Sep 23 06:36:47 Garuda-PC kernel: ACPI: HPET id: 0x10228201 base: 0xfed00000
Sep 23 06:36:47 Garuda-PC kernel: e820: update [mem 0xd6c25000-0xd6c65fff] usable ==> reserved
Sep 23 06:36:47 Garuda-PC kernel: smpboot: Allowing 32 CPUs, 24 hotplug CPUs
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x09d00000-0x09ffffff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x0a200000-0x0a20afff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0x0b000000-0x0b01ffff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xd6c25000-0xd6c65fff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xd92d3000-0xd92d3fff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xda466000-0xdb944fff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdbac5000-0xdbed3fff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdbed4000-0xdcc45fff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdcc46000-0xdccd6fff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xdf000000-0xdfffffff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xf7ffffff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfc000000-0xfcffffff]
Sep 23 06:36:47 Garuda-PC kernel: PM: hibernation: Registered nosave memory: [mem 0xfd000000-0xffffffff]
Sep 23 06:36:47 Garuda-PC kernel: [mem 0xe0000000-0xf7ffffff] available for PCI devices
Sep 23 06:36:47 Garuda-PC kernel: Booting paravirtualized kernel on bare hardware
Sep 23 06:36:47 Garuda-PC kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
Sep 23 06:36:47 Garuda-PC kernel: setup_percpu: NR_CPUS:320 nr_cpumask_bits:320 nr_cpu_ids:32 nr_node_ids:1
Sep 23 06:36:47 Garuda-PC kernel: percpu: Embedded 57 pages/cpu s196608 r8192 d28672 u262144
Sep 23 06:36:47 Garuda-PC kernel: pcpu-alloc: s196608 r8192 d28672 u262144 alloc=1*2097152
Sep 23 06:36:47 Garuda-PC kernel: pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15 
Sep 23 06:36:47 Garuda-PC kernel: pcpu-alloc: [0] 16 17 18 19 20 21 22 23 [0] 24 25 26 27 28 29 30 31 
Sep 23 06:36:47 Garuda-PC kernel: Built 1 zonelists, mobility grouping on.  Total pages: 8239423
Sep 23 06:36:47 Garuda-PC kernel: Policy zone: Normal
Sep 23 06:36:47 Garuda-PC kernel: Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=e63fe665-d42b-482a-aaf3-0fff940dd352 rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3
Sep 23 06:36:47 Garuda-PC kernel: Unknown command line parameters: splash BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
Sep 23 06:36:47 Garuda-PC kernel: printk: log_buf_len individual max cpu contribution: 4096 bytes
Sep 23 06:36:47 Garuda-PC kernel: printk: log_buf_len total cpu_extra contributions: 126976 bytes
Sep 23 06:36:47 Garuda-PC kernel: printk: log_buf_len min size: 131072 bytes
Sep 23 06:36:47 Garuda-PC kernel: printk: log_buf_len: 262144 bytes
Sep 23 06:36:47 Garuda-PC kernel: printk: early log buf free: 119368(91%)
Sep 23 06:36:47 Garuda-PC kernel: Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
Sep 23 06:36:47 Garuda-PC kernel: Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
Sep 23 06:36:47 Garuda-PC kernel: mem auto-init: stack:byref_all(zero), heap alloc:on, heap free:off
Sep 23 06:36:47 Garuda-PC kernel: Memory: 32641544K/33481484K available (16392K kernel code, 2090K rwdata, 9284K rodata, 1840K init, 3884K bss, 839680K reserved, 0K cma-reserved)
Sep 23 06:36:47 Garuda-PC kernel: random: get_random_u64 called from __kmem_cache_create+0x2c/0x6a0 with crng_init=0
Sep 23 06:36:47 Garuda-PC kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=32, Nodes=1
Sep 23 06:36:47 Garuda-PC kernel: ftrace: allocating 40579 entries in 159 pages
Sep 23 06:36:47 Garuda-PC kernel: ftrace: allocated 159 pages with 6 groups
Sep 23 06:36:47 Garuda-PC kernel: rcu: Preemptible hierarchical RCU implementation.
Sep 23 06:36:47 Garuda-PC kernel: rcu:         RCU dyntick-idle grace-period acceleration is enabled.
Sep 23 06:36:47 Garuda-PC kernel: rcu:         RCU restricting CPUs from NR_CPUS=320 to nr_cpu_ids=32.
Sep 23 06:36:47 Garuda-PC kernel: rcu:         RCU priority boosting: priority 1 delay 500 ms.
Sep 23 06:36:47 Garuda-PC kernel:         Trampoline variant of Tasks RCU enabled.
Sep 23 06:36:47 Garuda-PC kernel:         Rude variant of Tasks RCU enabled.
Sep 23 06:36:47 Garuda-PC kernel:         Tracing variant of Tasks RCU enabled.
Sep 23 06:36:47 Garuda-PC kernel: rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
Sep 23 06:36:47 Garuda-PC kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=32
Sep 23 06:36:47 Garuda-PC kernel: NR_IRQS: 20736, nr_irqs: 1224, preallocated irqs: 16
Sep 23 06:36:47 Garuda-PC kernel: kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval____)-0x(____ptrval____)
Sep 23 06:36:47 Garuda-PC kernel: Console: colour dummy device 80x25
Sep 23 06:36:47 Garuda-PC kernel: printk: console [tty0] enabled
[...]

$ journalctl -b-2


-- Journal begins at Sun 2021-09-12 14:04:11 WIB, ends at Thu 2021-09-23 07:00:02 WIB. --
Sep 22 22:11:31 Garuda-PC kernel: Linux version 5.14.2-zen1-2-zen (linux-zen@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 ZEN SMP PREEMPT Thu, 09 Sep 2021 09:42:32 +0000
Sep 22 22:11:31 Garuda-PC kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=e63fe665-d42b-482a-aaf3-0fff940dd352 rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3
Sep 22 22:11:31 Garuda-PC kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[...]

(untruncated)

Yeah, I don't think it gets to that point, seeing that it seems last boot was my previous, successful boot with the unmodified linux-zen kernel, where I did the mkinitcpio and then reboot. Just in case I checked both -b-2 and -b, they both shows me booting to linux-zen too. No linux-lts seen.

tbg · 23 September 2021 00:56

Perhaps it might be worth testing the fallback kernel from the grub boot menu.

fenglengshun · 23 September 2021 00:58

I made sure to test the fallback initramfs too, it's the same. Which really confused me.

tbg · 23 September 2021 01:01

Maybe give linux-hardened a try.