I was wondering if that kernel supports qr codes when a kernel panic occurs? I saw that is a new feature.
Also, what would be the steps to follow to debug a kernel panic to know the reason for what is hapenning? I think it is happening to my notebook (Thinkpad e16 gen 6 with core ultra 7 155h, intel arc graphics, 32gb ram, 2x1tb nvme), the caps lock key blinks and then the pc reboots
What makes you think that the kernel of the GNOME edition would be any different from the one used in the Plasma or Xfce editions? GNOME is a desktop environment, which runs atop the operating system.
As for whether the kernel has the QR code upon panic or not, this depends on the kernel version you are running. All kernels as of 5.15 contain the routines for showing a QR code upon panicking.
The blinking of modifier key LEDs is usually a sign of a hardware failure of some sorts, and given that your system immediately reboots when this happens, and that it is a notebook, I am inclined to suspect overheating as the cause.
Either way, even though there is no guarantee that you’d find any pointers to the actual panic after the reboot — when the kernel panics, it halts all operation, including logging — you might still be able to find some information via dmesg or journalctl. Please see their man pages for details.
The kernel need to be build with specific switch enabled and the kernel need being 6.12 or newer.
Manjaro kernels is configured to use kmsg as can be seen from the configs
Manjaro does not support the scenario and I am not a kernel developer so I have no idea - but it stands to reason that first task is to compile a kernel with the qr-code enabled.
Because Manjaro patches the kernel for several vendor specifics and does not (yet) support qr-code panic screen, it may be difficult to get the debug info accepted upstream.
My suggestion is to clone the linux-next-git package from AUR, build and install the kernel.
git clone https://aur.archlinux.org/linux-next-git
cd linux-next-git
makepkg -is
The config is configured with qr-code and may provide you with the required information and I am guessing the link is somehow translating the qr-code data into something human - but it is a guess
snipped from the linux-next-git PKGBUILD config file
CONFIG_DRM_PANIC=y
CONFIG_DRM_PANIC_FOREGROUND_COLOR=0xffffff
CONFIG_DRM_PANIC_BACKGROUND_COLOR=0x0000aa
# CONFIG_DRM_PANIC_DEBUG is not set
CONFIG_DRM_PANIC_SCREEN="qr_code"
CONFIG_DRM_PANIC_SCREEN_QR_CODE=y
CONFIG_DRM_PANIC_SCREEN_QR_CODE_URL="https://panic.archlinux.org/panic_report#"
CONFIG_DRM_PANIC_SCREEN_QR_VERSION=40
As pointed out by the config used by Arch there needs to be a backend like https://panic.archlinux.org/panic_report# to make it work. That we don’t have yet setup on our end. Hence kmsg is used to display the panic message instead.