[SOLVED] System freezes in Loading initial ramdisk

OnlyMinimum · 2022-02-03 22:53:16

Hello,

As usual, I weekly do my system upgrades with pacman -Syu, and the kernel has been upgraded to version 5.16.5.arch1-1 among other package updates. The problem is that I rebooted my computer and my system does not start, freezing with the message "Loading initial ramdisk..."

And then I am forced to restart the computer and use the LTS kernel in version 5.15.14-1-lts.

This is the second time this problem has happened, because previously (on 14/01/2022) I did a kernel update (5.15.13.arch1-1 to 5.16.arch1-1) and this problem happened again, so I thought it was a kernel bug or another problem, so I downgraded the kernel and also downloaded a version of the LTS kernel (5.15.14-1-lts) if I had another problem like that.

But when I tried to update the kernel today, as it was quoted at the beginning, I had this problem again, so I discarded that it is a kernel problem, but another problem.

With the contextualization of the problem made, how can I solve this problem?

I hope that I can help investigate the reasons and that we can solve the problem. Also, I apologize for my writing in English as it is not my native language.

Last edited by OnlyMinimum (2022-02-05 10:32:33)

squeaks · 2022-02-04 07:29:26

See https://wiki.archlinux.org/title/Genera … ow_to_post.

More information is needed. What are the general specifications of your system, are you booting in BIOS CSM or UEFI mode, how many displays are attached, where is your initramfs located, where is your efi partition, etc?

Some logs of failed and successful boots would be useful. See https://wiki.archlinux.org/title/Genera … t_problems

OnlyMinimum · 2022-02-04 14:45:28

Hi,

I appreciate the answer.
The specifications of my computer are:

Kernel: 5.15.14-1-lts
CPU: Intel i5-4440
RAM: 8GB
Motherboard: JGINYUE H97M-VH PLUS
Number of displays attached: 2
Machine running in UEFI mode

About partitions:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 238.5G  0 disk 
├─sda1   8:1    0   500M  0 part /boot/efi
├─sda2   8:2    0   135G  0 part /
├─sda3   8:3    0    90G  0 part /home
└─sda4   8:4    0    13G  0 part [SWAP]

About initramfs location:

/etc/mkinitcpio.conf

/etc/mkinitcpio.d:
linux-lts.preset  linux.preset

OnlyMinimum · 2022-02-04 15:11:13

About the logs:

Running journalctl -b 3 (is a successful boot):

Feb 03 14:20:11 arch-mkIV kernel: microcode: microcode updated early to revision 0x28, date = 2019-11-12
Feb 03 14:20:11 arch-mkIV kernel: Linux version 5.15.14-1-lts (linux-lts@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP Tue, 11 Jan 2022 15:37:45 +0000
Feb 03 14:20:11 arch-mkIV kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=e071274c-b369-461d-af1f-e91f6ae43a4c rw loglevel=3 quiet
Feb 03 14:20:11 arch-mkIV kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Feb 03 14:20:11 arch-mkIV kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Feb 03 14:20:11 arch-mkIV kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Feb 03 14:20:11 arch-mkIV kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Feb 03 14:20:11 arch-mkIV kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Feb 03 14:20:11 arch-mkIV kernel: signal: max sigframe size: 1776
Feb 03 14:20:11 arch-mkIV kernel: BIOS-provided physical RAM map:
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x0000000000100000-0x000000009530afff] usable
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x000000009530b000-0x0000000095369fff] reserved
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x000000009536a000-0x0000000095559fff] usable
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x000000009555a000-0x0000000095cdefff] ACPI NVS
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x0000000095cdf000-0x0000000095fb0fff] reserved
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x0000000095fb1000-0x0000000095ffefff] type 20
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x0000000095fff000-0x0000000095ffffff] usable
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x0000000097000000-0x00000000a71fffff] reserved
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 03 14:20:11 arch-mkIV kernel: BIOS-e820: [mem 0x0000000100000000-0x0000000257dfffff] usable
Feb 03 14:20:11 arch-mkIV kernel: NX (Execute Disable) protection: active
Feb 03 14:20:11 arch-mkIV kernel: efi: EFI v2.40 by American Megatrends
Feb 03 14:20:11 arch-mkIV kernel: efi: ESRT=0x95fad198 ACPI=0x95ca0000 ACPI 2.0=0x95ca0000 SMBIOS=0xf05b0 SMBIOS 3.0=0x95ef0000 
Feb 03 14:20:11 arch-mkIV kernel: SMBIOS 3.0.0 present.
Feb 03 14:20:11 arch-mkIV kernel: DMI: Default string Default string/H97M-VH PLUS, BIOS 5.6.5 03/16/2021
Feb 03 14:20:11 arch-mkIV kernel: tsc: Fast TSC calibration using PIT
Feb 03 14:20:11 arch-mkIV kernel: tsc: Detected 3093.110 MHz processor
Feb 03 14:20:11 arch-mkIV kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 03 14:20:11 arch-mkIV kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 03 14:20:11 arch-mkIV kernel: last_pfn = 0x257e00 max_arch_pfn = 0x400000000
Feb 03 14:20:11 arch-mkIV kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Feb 03 14:20:11 arch-mkIV kernel: total RAM covered: 7902M
Feb 03 14:20:11 arch-mkIV kernel: Found optimal setting for mtrr clean up
Feb 03 14:20:11 arch-mkIV kernel:  gran_size: 64K         chunk_size: 4M         num_reg: 9          lose cover RAM: 0G
Feb 03 14:20:11 arch-mkIV kernel: e820: update [mem 0x96000000-0xffffffff] usable ==> reserved
Feb 03 14:20:11 arch-mkIV kernel: last_pfn = 0x96000 max_arch_pfn = 0x400000000
Feb 03 14:20:11 arch-mkIV kernel: found SMP MP-table at [mem 0x000fd910-0x000fd91f]
Feb 03 14:20:11 arch-mkIV kernel: esrt: Reserving ESRT space from 0x0000000095fad198 to 0x0000000095fad1d0.
Feb 03 14:20:11 arch-mkIV kernel: Using GB pages for direct mapping
Feb 03 14:20:11 arch-mkIV kernel: Secure boot disabled
Feb 03 14:20:11 arch-mkIV kernel: RAMDISK: [mem 0x365f5000-0x372f1fff]
Feb 03 14:20:11 arch-mkIV kernel: ACPI: Early table checksum verification disabled
Feb 03 14:20:11 arch-mkIV kernel: ACPI: RSDP 0x0000000095CA0000 000024 (v02 ALASKA)
Feb 03 14:20:11 arch-mkIV kernel: ACPI: XSDT 0x0000000095CA0098 0000B4 (v01 ALASKA A M I    01072009 AMI  00010013)
Feb 03 14:20:11 arch-mkIV kernel: ACPI: FACP 0x0000000095CB6528 00010C (v05 ALASKA A M I    01072009 AMI  00010013)
...skipping...
Feb 03 19:07:03 arch-mkIV systemd[1]: tmp.mount: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV systemd[1]: Unmounted Temporary Directory /tmp.
Feb 03 19:07:03 arch-mkIV systemd[1]: Stopped target Swaps.
Feb 03 19:07:03 arch-mkIV systemd[1]: Deactivating swap /dev/disk/by-id/ata-SSD_256GB_202012150617-part4...
Feb 03 19:07:03 arch-mkIV systemd[1]: home.mount: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV systemd[1]: Unmounted /home.
Feb 03 19:07:03 arch-mkIV systemd[1]: systemd-fsck@dev-disk-by\x2duuid-59aac63d\x2d0065\x2d4d8c\x2db38e\x2d46d78aba63e6.service: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV systemd[1]: Stopped File System Check on /dev/disk/by-uuid/59aac63d-0065-4d8c-b38e-46d78aba63e6.
Feb 03 19:07:03 arch-mkIV audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-59aac63d\x2d0065\x2d4d8c\x2db38e\x2d46d78aba63e6 comm="systemd" exe="/u>
Feb 03 19:07:03 arch-mkIV systemd[1]: Removed slice Slice /system/systemd-fsck.
Feb 03 19:07:03 arch-mkIV systemd[1]: Stopped target Preparation for Local File Systems.
Feb 03 19:07:03 arch-mkIV systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Feb 03 19:07:03 arch-mkIV systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV systemd[1]: Stopped Create Static Device Nodes in /dev.
Feb 03 19:07:03 arch-mkIV audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re>
Feb 03 19:07:03 arch-mkIV systemd[1]: systemd-sysusers.service: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 19:07:03 arch-mkIV systemd[1]: Stopped Create System Users.
Feb 03 19:07:03 arch-mkIV audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes>
Feb 03 19:07:03 arch-mkIV systemd[1]: systemd-remount-fs.service: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV systemd[1]: Stopped Remount Root and Kernel File Systems.
Feb 03 19:07:03 arch-mkIV systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart4.swap: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0-part4.
Feb 03 19:07:03 arch-mkIV systemd[1]: dev-disk-by\x2did-ata\x2dSSD_256GB_202012150617\x2dpart4.swap: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV systemd[1]: Deactivated swap /dev/disk/by-id/ata-SSD_256GB_202012150617-part4.
Feb 03 19:07:03 arch-mkIV systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart4.swap: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:1f.2-ata-1-part4.
Feb 03 19:07:03 arch-mkIV systemd[1]: dev-disk-by\x2dpartuuid-875168b3\x2d7fbe\x2d574e\x2d8fa5\x2d08c457a12b75.swap: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV systemd[1]: Deactivated swap /dev/disk/by-partuuid/875168b3-7fbe-574e-8fa5-08c457a12b75.
Feb 03 19:07:03 arch-mkIV systemd[1]: dev-sda4.swap: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV systemd[1]: Deactivated swap /dev/sda4.
Feb 03 19:07:03 arch-mkIV systemd[1]: dev-disk-by\x2duuid-3954caf3\x2dafb1\x2d4e38\x2d8b89\x2d3940eaa6ea03.swap: Deactivated successfully.
Feb 03 19:07:03 arch-mkIV systemd[1]: Deactivated swap /dev/disk/by-uuid/3954caf3-afb1-4e38-8b89-3940eaa6ea03.
Feb 03 19:07:03 arch-mkIV systemd[1]: Reached target Unmount All Filesystems.
Feb 03 19:07:04 arch-mkIV systemd[1]: lvm2-monitor.service: Deactivated successfully.
Feb 03 19:07:04 arch-mkIV systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Feb 03 19:07:04 arch-mkIV audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 19:07:04 arch-mkIV systemd[1]: Reached target System Shutdown.
Feb 03 19:07:04 arch-mkIV systemd[1]: Reached target Late Shutdown Services.
Feb 03 19:07:04 arch-mkIV systemd[1]: systemd-poweroff.service: Deactivated successfully.
Feb 03 19:07:04 arch-mkIV audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 19:07:04 arch-mkIV audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 19:07:04 arch-mkIV systemd[1]: Finished System Power Off.
Feb 03 19:07:04 arch-mkIV systemd[1]: Reached target System Power Off.
Feb 03 19:07:04 arch-mkIV systemd[1]: Shutting down.
Feb 03 19:07:04 arch-mkIV audit: BPF prog-id=0 op=UNLOAD
Feb 03 19:07:04 arch-mkIV audit: BPF prog-id=0 op=UNLOAD
Feb 03 19:07:04 arch-mkIV audit: BPF prog-id=0 op=UNLOAD
Feb 03 19:07:04 arch-mkIV audit: BPF prog-id=0 op=UNLOAD
Feb 03 19:07:04 arch-mkIV audit: BPF prog-id=0 op=UNLOAD
Feb 03 19:07:04 arch-mkIV audit: BPF prog-id=0 op=UNLOAD
Feb 03 19:07:04 arch-mkIV systemd-shutdown[1]: Syncing filesystems and block devices.
Feb 03 19:07:04 arch-mkIV systemd-journald[223]: Journal stopped

About the failed boot: I don't know how to get the unsuccessful boot log.
I tried to get the boot log at the time the failure occurred with

 journalctl -b -4

but it didn't show the same messages I got when I changed the kernel boot parameter to

loglevel=7

and removing the

quiet

parameter.
How i can get the the unsuccessful boot log? I really don't know, sorry.

Last edited by OnlyMinimum (2022-02-04 15:13:16)

squeaks · 2022-02-04 19:31:49

What I'm interested in is whether your system actually freezes. It sounds like you have one monitor connected to your iGPU and probably another monitor to a discrete video card?

Also try 'journalctl -k -b X', where X is the boot you're interested. You snipped way too soon in your log. I'm looking for frame buffer, console, and related driver output.

Show 'lspci -k' Can you provide 'cat /proc/fb'.

What I'm trying to see is if your frozen boots are actually running but with a configuration problem with the console.

For instance, it could be possible the kernel is loading fine but switching it's display output to an incorrect or unexpected output.

The kernel developers do seem to be making changes, see https://github.com/torvalds/linux/commi … b_helper.c, and logically feedback could be useful to them. It's beyond my capability to help you bisect your kernel problems, but I suspect that would be next steps. You'd determine which version of the kernel caused the problem and follow their procedures for bug reporting.

You can try more of what's found at https://wiki.archlinux.org/title/Genera … t_problems.

seth · 2022-02-04 20:46:50

And then I am forced to restart the computer and use the LTS kernel in version 5.15.14-1-lts.

ctrl+alt+del or power button? If the latter is required, try https://wiki.archlinux.org/title/Keyboa … el_(SysRq) - a hardreset will prevent the journal from being written to disk.

If you raise the debug level, https://wiki.archlinux.org/title/Genera … bug_output do you get some usable output for the freeze (in doubt make a photo)

OnlyMinimum · 2022-02-04 21:05:56

squeaks wrote:

What I'm interested in is whether your system actually freezes. It sounds like you have one monitor connected to your iGPU and probably another monitor to a discrete video card?
Also try 'journalctl -k -b X', where X is the boot you're interested. You snipped way too soon in your log. I'm looking for frame buffer, console, and related driver output.

I've tried using this command, but the output I get doesn't contain the time range when the freeze happens.

Running lspci -k:

00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
	Subsystem: Intel Corporation 4th Gen Core Processor DRAM Controller
	Kernel driver in use: hsw_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
	Kernel driver in use: pcieport
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
	DeviceName:  Onboard IGD
	Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
	Kernel driver in use: i915
	Kernel modules: i915
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 2 (rev d0)
	Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0)
	Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Z97 Chipset LPC Controller
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01)
	Subsystem: Realtek Semiconductor Co., Ltd. Device 8197
	Kernel driver in use: rtl8188ee
	Kernel modules: rtl8188ee
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
	Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
	Kernel driver in use: r8169
	Kernel modules: r8169

Running cat /proc/fb:

0 i915drmfb

What I found strange with all this happening is that this same problem happened with two kernel versions, but with version 5.15.13.arch1-1 (which is the version I've been using) I don't have this problem, which even, the first time this happened after the update (update to 5.16.arch1-1), as a temporary fix I downgraded it, via a bootable USB stick with the Arch Linux installation iso, hoping that in the next kernel update this problem no longer exists.

In case it helps, here is the output of the command 'cat /var/log/pacman.log | grep "upgraded linux"':

[2021-12-15T18:56:40-0300] [ALPM] upgraded linux (5.15.7.arch1-1 -> 5.15.8.arch1-1)
[2021-12-18T18:28:09-0300] [ALPM] upgraded linux (5.15.8.arch1-1 -> 5.15.10.arch1-1)
[2021-12-27T10:25:56-0300] [ALPM] upgraded linux (5.15.10.arch1-1 -> 5.15.11.arch2-1)
[2021-12-30T14:33:32-0300] [ALPM] upgraded linux (5.15.11.arch2-1 -> 5.15.12.arch1-1)
[2022-01-06T14:08:04-0300] [ALPM] upgraded linux (5.15.12.arch1-1 -> 5.15.13.arch1-1)
[2022-01-14T18:16:06-0300] [ALPM] upgraded linux (5.15.13.arch1-1 -> 5.16.arch1-1)                  <-------- First ocurrence of problem
[2022-01-14T18:16:10-0300] [ALPM] upgraded linux-firmware (20211027.1d00989-1 -> 20211216.f682ecb-1)
[2022-01-23T22:17:10-0300] [ALPM] upgraded linux-firmware (20211216.f682ecb-1 -> 20220119.0c6a7b3-2)
[2022-02-03T14:11:16-0300] [ALPM] upgraded linux (5.15.13.arch1-1 -> 5.16.5.arch1-1)                <-------- Second ocurrence of problem

OnlyMinimum · 2022-02-04 21:31:23

seth wrote:

And then I am forced to restart the computer and use the LTS kernel in version 5.15.14-1-lts.
ctrl+alt+del or power button? If the latter is required, try https://wiki.archlinux.org/title/Keyboa … el_(SysRq) - a hardreset will prevent the journal from being written to disk.
If you raise the debug level, https://wiki.archlinux.org/title/Genera … bug_output do you get some usable output for the freeze (in doubt make a photo)

I make these modifications to raise the debug level, but I am forced to press the power button (hard reset) to shut down the computer. I think that's why these log messages don't show up in the registry.
In this case I will send a photo and here is the link. I apologize for the quality of the image because I had to compress the image to follow the forum rules.

https://i.imgur.com/adRLcuo.jpg

Last edited by OnlyMinimum (2022-02-04 21:33:03)

OnlyMinimum · 2022-02-04 21:42:36

squeaks wrote:

What I'm interested in is whether your system actually freezes. It sounds like you have one monitor connected to your iGPU and probably another monitor to a discrete video card?

Ah, I forgot to comment: I only have the CPU's integrated graphics. The two monitors are connected directly to the motherboard (one VGA and one HDMI input).

seth · 2022-02-04 21:44:52

The forum rules don't restrict the size of linked images (only embedded ones)
Looks like https://bbs.archlinux.org/viewtopic.php?id=273295

OnlyMinimum · 2022-02-04 21:57:15

seth wrote:

The forum rules don't restrict the size of linked images (only embedded ones)
Looks like https://bbs.archlinux.org/viewtopic.php?id=273295

Ah, I thought this rule applies to all images. Thanks.

squeaks wrote:

What I'm interested in is whether your system actually freezes. It sounds like you have one monitor connected to your iGPU and probably another monitor to a discrete video card?

And out of curiosity, I tried turning on the machine using the problematic kernel, this time using just one monitor and the problem persists.

A new output of the error. After a few seconds, the messages are the same as the image I posted earlier.
https://imgur.com/a/TrNyMNq

seth · 2022-02-04 22:08:44

There's a kernel w/ a pot. fix in the other thread, https://bbs.archlinux.org/viewtopic.php … 8#p2018268

OnlyMinimum · 2022-02-04 22:16:59

seth wrote:

There's a kernel w/ a pot. fix in the other thread, https://bbs.archlinux.org/viewtopic.php … 8#p2018268

Okay, I read this thread and the kernel fix is in post #53. I'm going to install the kernel and run the tests.

OnlyMinimum · 2022-02-04 22:36:33

seth wrote:

There's a kernel w/ a pot. fix in the other thread, https://bbs.archlinux.org/viewtopic.php … 8#p2018268

Gentlemen, this fix works normally, even I'm already using it.
Running uname -a:

Linux arch-mkIV 5.16.2-arch1-1.1 #1 SMP PREEMPT Tue, 25 Jan 2022 16:54:53 +0000 x86_64 GNU/Linux

Now am I going to ignore the kernel update by modifying the pacman.conf file, until I see another version and I'll test it again, or isn't that a good idea from a system maintenance point of view?

Although I don't have the technical knowledge necessary to work with kernel development and debugging, is there anything else I can contribute? If so, how can I do it?

My sincere thanks.

seth · 2022-02-05 07:41:57

There's an upstream bug you might want to look at. Since this is - likely - drive specific, you should record yours for comparism (and if a quirk is required)

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

OnlyMinimum · 2022-02-05 10:28:02

Okay, I'll look at the upstream bug report.

I believe moderators/administrators can close this thread now.

Arch Linux

#1 2022-02-03 22:53:16

[SOLVED] System freezes in Loading initial ramdisk

#2 2022-02-04 07:29:26

Re: [SOLVED] System freezes in Loading initial ramdisk

#3 2022-02-04 14:45:28

Re: [SOLVED] System freezes in Loading initial ramdisk

#4 2022-02-04 15:11:13

Re: [SOLVED] System freezes in Loading initial ramdisk

#5 2022-02-04 19:31:49

Re: [SOLVED] System freezes in Loading initial ramdisk

#6 2022-02-04 20:46:50

Re: [SOLVED] System freezes in Loading initial ramdisk

#7 2022-02-04 21:05:56

Re: [SOLVED] System freezes in Loading initial ramdisk

#8 2022-02-04 21:31:23

Re: [SOLVED] System freezes in Loading initial ramdisk

#9 2022-02-04 21:42:36

Re: [SOLVED] System freezes in Loading initial ramdisk

#10 2022-02-04 21:44:52

Re: [SOLVED] System freezes in Loading initial ramdisk

#11 2022-02-04 21:57:15

Re: [SOLVED] System freezes in Loading initial ramdisk

#12 2022-02-04 22:08:44

Re: [SOLVED] System freezes in Loading initial ramdisk

#13 2022-02-04 22:16:59

Re: [SOLVED] System freezes in Loading initial ramdisk

#14 2022-02-04 22:36:33

Re: [SOLVED] System freezes in Loading initial ramdisk

#15 2022-02-05 07:41:57

Re: [SOLVED] System freezes in Loading initial ramdisk

#16 2022-02-05 10:28:02

Re: [SOLVED] System freezes in Loading initial ramdisk

Board footer