Public bug reported:
Hello,
I am experiencing a 100% reproducible kernel regression (on my machine)
that causes an instant system reboot when launching a specific Flatpak
application. The system was previously experiencing random kernel
panics, which were thought to have been resolved by purging a
conflicting system-wide ROCm installation.
What I expected to happen:
The Flatpak application 'Supercell WX' should launch normally.
What happened instead:
The moment the application is launched, the system instantly reboots
without displaying a visual kernel panic message on screen. No "Kernel
Panic" or "BUG" messages are written to the journalctl logs from the
crashed boot; the log simply cuts off.
---
CRITICAL EVIDENCE OF REGRESSION:
---
This crash ONLY occurs on the newer kernel. The application runs
perfectly on the older kernel.
* BAD KERNEL (crashes): 6.14.0-24-generic
* GOOD KERNEL (works mostly perfectly): 6.11.0-29-generic
g30@g30-Z690-AORUS-MASTER:~$ uname -r
6.11.0-29-generic
---
SYSTEM AND APPLICATION DETAILS:
---
1. Release of Ubuntu:
g30@g30-Z690-AORUS-MASTER:~$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 24.04.2 LTS
Release: 24.04
2. Trigger Application Information (Flatpak):
The crash is triggered by launching the Flatpak application
net.supercellwx.app.
Runtime: org.freedesktop.Platform/x86_64/23.08
3. Graphics Hardware Information:
g30@g30-Z690-AORUS-MASTER:~$ sudo lshw -C display
[sudo] password for g30:
*-display
description: VGA compatible controller
product: Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:03:00.0
logical name: /dev/fb0
version: c1
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master
cap_list rom fb
configuration: depth=32 driver=amdgpu latency=0
resolution=2560,1440
resources: irq:238 memory:60000000-6fffffff
memory:70000000-701fffff ioport:4000(size=256) memory:43000000-430fffff
memory:43100000-4311ffff
*-display
description: VGA compatible controller
product: AlderLake-S GT1
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 0c
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master
cap_list rom
configuration: driver=i915 latency=0
resources: irq:235 memory:41000000-41ffffff
memory:50000000-5fffffff ioport:5000(size=64) memory:c0000-dffff
memory:44000000-4affffff
---
LOGS:
---
I have attached the required logs version.log and lspci-vnvn.log
(generated while booted into the problematic kernel 6.14.0-24-generic).
version.log file content: Ubuntu 6.14.0-24.24~24.04.3-generic 6.14.6
Due to the nature of the instant reboot, a full crash log is not
available in journalctl. The log from the previous boot journalctl -b
-1) simply ends without any specific error messages related to the crash
itself, showing only normal system activity up to the point of the
reboot.
Thank you for your time.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amdgpu flatpak kernel-panic noble regression
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/bugs/2117328/+attachment/5891501/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2117328
Title:
Kernel Regression in 6.14.0-24-generic causes instant reboot with
amdgpu when launching specific Flatpak app
Status in linux package in Ubuntu:
New
Bug description:
Hello,
I am experiencing a 100% reproducible kernel regression (on my
machine) that causes an instant system reboot when launching a
specific Flatpak application. The system was previously experiencing
random kernel panics, which were thought to have been resolved by
purging a conflicting system-wide ROCm installation.
What I expected to happen:
The Flatpak application 'Supercell WX' should launch normally.
What happened instead:
The moment the application is launched, the system instantly reboots
without displaying a visual kernel panic message on screen. No "Kernel
Panic" or "BUG" messages are written to the journalctl logs from the
crashed boot; the log simply cuts off.
---
CRITICAL EVIDENCE OF REGRESSION:
---
This crash ONLY occurs on the newer kernel. The application runs
perfectly on the older kernel.
* BAD KERNEL (crashes): 6.14.0-24-generic
* GOOD KERNEL (works mostly perfectly): 6.11.0-29-generic
g30@g30-Z690-AORUS-MASTER:~$ uname -r
6.11.0-29-generic
---
SYSTEM AND APPLICATION DETAILS:
---
1. Release of Ubuntu:
g30@g30-Z690-AORUS-MASTER:~$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 24.04.2 LTS
Release: 24.04
2. Trigger Application Information (Flatpak):
The crash is triggered by launching the Flatpak application
net.supercellwx.app.
Runtime: org.freedesktop.Platform/x86_64/23.08
3. Graphics Hardware Information:
g30@g30-Z690-AORUS-MASTER:~$ sudo lshw -C display
[sudo] password for g30:
*-display
description: VGA compatible controller
product: Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:03:00.0
logical name: /dev/fb0
version: c1
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master
cap_list rom fb
configuration: depth=32 driver=amdgpu latency=0
resolution=2560,1440
resources: irq:238 memory:60000000-6fffffff
memory:70000000-701fffff ioport:4000(size=256)
memory:43000000-430fffff memory:43100000-4311ffff
*-display
description: VGA compatible controller
product: AlderLake-S GT1
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 0c
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master
cap_list rom
configuration: driver=i915 latency=0
resources: irq:235 memory:41000000-41ffffff
memory:50000000-5fffffff ioport:5000(size=64) memory:c0000-dffff
memory:44000000-4affffff
---
LOGS:
---
I have attached the required logs version.log and lspci-vnvn.log
(generated while booted into the problematic kernel
6.14.0-24-generic).
version.log file content: Ubuntu 6.14.0-24.24~24.04.3-generic 6.14.6
Due to the nature of the instant reboot, a full crash log is not
available in journalctl. The log from the previous boot journalctl -b
-1) simply ends without any specific error messages related to the
crash itself, showing only normal system activity up to the point of
the reboot.
Thank you for your time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2117328/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
