
| Msg # 1145 of 1332 on ZZLI4424, Sunday 9-06-25, 8:04 |
| From: SALVATORE BONACCORSO |
| To: WILLED-ANVIL-ELUDE@DUCK.C |
| Subj: Bug#1113861: linux-image-6.12.41+deb13-a |
XPost: linux.debian.bugs.dist
From: carnil@debian.org
Control: tags -1 + moreinfo
On Wed, Sep 03, 2025 at 10:16:24AM -0400, willed-anvil-elude@duck.com wrote:
> Package: src:linux
> Version: 6.12.41-1
> Severity: important
> X-Debbugs-Cc: willed-anvil-elude@duck.com
>
> Dear Maintainer,
>
> Most Flatpak apps have suddenly broken on my Debian Stable ("Trixie")
> installation. They were working normally until I ran a `flatpak update`
today
> after several weeks without updating the Flatpak system, but now the apps
fail
> to launch. I have confirmed that the base OS runs fine until the first
time I
> launch a Flatpak app, at which point it causes a kernel oops in the
`nouveau`
> module.
>
> I tried completely uninstalling and reinstalling all Flatpak-related Debian
> packages, and I renamed `~/.local/share/flatpak` and `/var/lib/flatpak` and
> tried starting fresh with Flatpak, but it made no difference.
>
> My hardware is a laptop with hybrid Intel / Nvidia graphics, but I don't
use
> the Nvidia card at all. I even tried uninstalling the `xserver-xorg-video-
> nouveau` package, but somehow the `nouveau` module was still loading, I
imagine
> coming from the Flatpak environment.
>
> When I boot with the kernel command line `module_blacklist=nouveau` this
bug
> does **not** happen. This bug happens with the oldest Debian Trixie
released
> kernel version (6.12.31-amd64) as well as the latest one (6.12
41+deb13-amd64).
> What changed on my system leading to this bug was the Flatpak framework
> updates, however in my bug report to them
> (https://github.com/flatpak/flatpak/issues/6307) they say it's a kernel
bug.
>
> Here's the `dmesg` output that corresponds exactly to the moment that a
Flatpak
> app is launched:
>
> ```````````````````````````````````````````
> [Tue Sep 2 23:31:49 2025] BUG: kernel NULL pointer dereference, address:
> 0000000000000000
> [Tue Sep 2 23:31:49 2025] #PF: supervisor read access in kernel mode
> [Tue Sep 2 23:31:49 2025] #PF: error_code(0x0000) - not-present page
> [Tue Sep 2 23:31:49 2025] PGD 0 P4D 0
> [Tue Sep 2 23:31:49 2025] Oops: Oops: 0000 [#3] PREEMPT SMP PTI
> [Tue Sep 2 23:31:49 2025] CPU: 6 UID: 1000 PID: 4820 Comm: com.github.tchx
> Tainted: G D 6.12.31-amd64 #1 Debian 6.12.31-1
> [Tue Sep 2 23:31:49 2025] Tainted: [D]=DIE
> [Tue Sep 2 23:31:49 2025] Hardware name: Intel(R) Client Systems
> LAPQC71A/LAPQC71A, BIOS QCCFL357.0144.2022.0124.1433 01/24/2022
> [Tue Sep 2 23:31:49 2025] RIP: 0010:nvkm_gr_units+0x9/0x30 [nouveau]
> [Tue Sep 2 23:31:49 2025] Code: 74 06 ff e0 cc 66 90 cc 31 c0 c3 cc cc cc
cc
> 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 0f 1f 44
00
> 00 <48> 8b 07 48 8b 40 58 48 85 c0 74 06 ff e0 cc 66 90 cc 31 c0 c3 cc
> [Tue Sep 2 23:31:49 2025] RSP: 0018:ffffa1f38f267b40 EFLAGS: 00010246
> [Tue Sep 2 23:31:49 2025] RAX: ffff92a3ba38e000 RBX: ffffa1f38f267c20 RCX:
> ffff92a3871f2800
> [Tue Sep 2 23:31:49 2025] RDX: ffff92a599362c00 RSI: ffffa1f38f267c20 RDI:
> 0000000000000000
> [Tue Sep 2 23:31:49 2025] RBP: ffff92a4ab71d000 R08: 000000000000000d R09:
> 00000000000012d4
> [Tue Sep 2 23:31:49 2025] R10: 0000000000000010 R11: 0000000000000012 R12:
> ffffffffc0bb61f0
> [Tue Sep 2 23:31:49 2025] R13: ffffa1f38f267c20 R14: ffff92a3ba386000 R15:
> 0000000000000010
> [Tue Sep 2 23:31:49 2025] FS: 00007fe43b074940(0000)
> GS:ffff92ab1db00000(0000) knlGS:0000000000000000
> [Tue Sep 2 23:31:49 2025] CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
> [Tue Sep 2 23:31:49 2025] CR2: 0000000000000000 CR3: 000000030ae00001 CR4:
> 00000000003726f0
> [Tue Sep 2 23:31:49 2025] Call Trace:
> [Tue Sep 2 23:31:49 2025] |
328,084 visits
(c) 1994, bbs@darkrealms.ca