Hi All,
I’m having trouble logging in after doing distribution upgrade. It seem the issue is kernel 6.16. When it’s selected, I get to the graphical log in page and then CapsLock starts to blink and laptop goes into reboot. When I select previous version of the kernel (6.15) – no issues.
I’m new to debugging such issues, so this is what I tried:
$ sudo journalctl -b -1 -p 4 -k --no-pager
Sep 18 20:35:55 localhost kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Sep 18 20:35:56 localhost kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 18 20:35:56 localhost systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Sep 18 20:35:57 localhost kernel: ata1.00: Model 'Samsung SSD 860 EVO 500GB', rev 'RVT02B6Q', applying quirks: noncqtrim zeroaftertrim noncqonati nolpmonati
Sep 18 20:35:57 localhost kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 18 20:35:57 localhost kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 18 20:36:04 localhost systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Sep 18 20:36:04 localhost kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20250404/utaddress-204)
Sep 18 20:36:04 localhost kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20250404/utaddress-204)
Sep 18 20:36:04 localhost kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20250404/utaddress-204)
Sep 18 20:36:04 localhost kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20250404/utaddress-204)
Sep 18 20:36:04 localhost kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20250404/utaddress-204)
Sep 18 20:36:04 localhost kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000055F (\_SB.PCI0.PEG0.PEGP.GPIO) (20250404/utaddress-204)
Sep 18 20:36:04 localhost kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20250404/utaddress-204)
Sep 18 20:36:04 localhost kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 18 20:36:04 localhost kernel: iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
Sep 18 20:36:04 localhost kernel: r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
Sep 18 20:36:04 localhost kernel: Bluetooth: hci0: unexpected event for opcode 0x0000
Comparing this output to the output with working older kernel, the only major diff is Bluetooth error, but internet tells me that it’s not expected to cause issues with other systems.
Any recommendations on how to debug this are appreciated.
You may need to read that first URL in that journal output, and perhaps add or adjust a mitigation option on the bootloader’s linu line.
Is there a firmware/BIOS update available for your computer? ACPI trouble can be an errant BIOS issue.
An optional longterm support kernel 6.12.47 is available. You might install it to see if its behavior differs.
Please provide some information about your system. Paste here input/output from running command inxi -Faz --vs using the preformatted text object at the top of the composition input window to preserve the inxi command’s original formatting used on your own display. Do this booted to the working previous kernel, or if it works OK, the longterm kernel.
If you didn’t upgrade to 20250917 yet, do it.
This has variou ACPI override parameters you might wish to try on your bootloader’s linu line.
Thanks for the reply. Output of the command is below. Btw, it’s an old Samsung laptop.
How do I check for firmware/BIOS update? I haven’t done anything special for BIOS since I got the laptop decade ago. If you could point me to some instructions, that would be nice.
And I’ll read over docs in the first URL in journalctl, although admittedly it’ll take me a while to figure out how to add the fix from there.
@juicyplum Hi, so the AMD device is for Prime Render Offload only (3D - Class ID 380), I’d looking at switch that to amdgpu rather than radeon ( @mrmazda has info on that). Maybe define what gpu is going to perform Vulkan(?)
But that looks like a desktop issue rather than driver? Have you upgraded to the latest snapshot?
Including radeon.si_support=0 amdgpu.si_support=1 on your boot stanzas’ linu lines should disable the radeon kernel module and enable the amdgpu kernel module for your Device-2 AMD GCN#1 GPU, might make a difference. I’ve seen radeon kernel module trouble several places in recent months, but I’m not sure whether it’s been the module, or kernel-firmware-radeon where the troubles have stemmed from.
Thanks for the suggestions. I tried using radeon.si_support=0 amdgpu.si_support=1 in grub but that did not work. I also did distribution upgrade and lost my working 6.15 kernel I’ll try installing optional long term kernel for now.
To avoid this happening again, the limited number of installed kernels kept by default can be customized via multiversion.kernel in /etc/zypp/zypp.conf. It can also be avoided by manually removing a failing kernel before another is installed, and/or by disabling purge-kernels.service.
Thanks for your help. Looks like LTS kernel works fine, so I’m going to stick with that for a while.
I’ve updated zypp.conf to avoid losing it in the future.
I’ll try installing optional long term kernel for now.