Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #91780 > unrolled thread
| Started by | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| First post | 2026-03-23 19:50 +0100 |
| Last post | 2026-03-23 19:50 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1131626: linux-image-6.12.74+deb13+1-amd64: Hung thread leading to panic on removing amdgpu module Salvatore Bonaccorso <carnil@debian.org> - 2026-03-23 19:50 +0100
Processed: Re: Bug#1131626: linux-image-6.12.74+deb13+1-amd64: Hung thread leading to panic on removing amdgpu module "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-03-23 19:50 +0100
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2026-03-23 19:50 +0100 |
| Subject | Bug#1131626: linux-image-6.12.74+deb13+1-amd64: Hung thread leading to panic on removing amdgpu module |
| Message-ID | <MBSvE-9KTi-7@gated-at.bofh.it> |
Control: forcemerge 1130930 -1 Hi, On Mon, Mar 23, 2026 at 03:20:44PM +0800, James French wrote: > Package: src:linux > Version: 6.12.74-2 > Severity: important > X-Debbugs-Cc: james@french.id.au > > Dear Maintainer, > > Removing the amdgpu module after previously disconnecting the framebuffer results in a repeatable hung CPU and eventual kernel panic on kernels 6.12.74 and the previous security release 6.12.73. This worked in Bookworm and has worked in Trixie - Kernels 6.12.63 and earlier were not affected. > > >From the attached journal, this appears to be an issue with the amdgpu module failing to properly release the hardware. > > This bug breaks single GPU passthrough to a VM where the host may also use the card when it is not in use. Booting with amdgpu.dc=0,or with amdgpu blacklisted are workarounds, but do not allow the host to use the GPU when the guest is not in use. > > I have seen this behaviour on three systems with an RX 6000 and RX 7000 series cards. This should be the same as the already reported #1130930, merging both. It will be fixed with the next upload for trixie. But if you can, test the mentioned commit on top of 6.12.74-1 to confirm, would be great! Regards, Salvatore
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2026-03-23 19:50 +0100 |
| Subject | Processed: Re: Bug#1131626: linux-image-6.12.74+deb13+1-amd64: Hung thread leading to panic on removing amdgpu module |
| Message-ID | <MBSvE-9KTi-11@gated-at.bofh.it> |
| In reply to | #91780 |
Processing control commands: > forcemerge 1130930 -1 Bug #1130930 [src:linux] linux-image-6.12.74+deb13+1-amd64: Kernel-6.12.74+deb 13+1-amd64 fail/stuck to Unload AMD driver for single gpu passthrough Bug #1131626 [src:linux] linux-image-6.12.74+deb13+1-amd64: Hung thread leading to panic on removing amdgpu module Set Bug forwarded-to-address to 'https://lore.kernel.org/regressions/1be114e1130ca59ee91fc5a73aaf43a912d408ea@qpok.net'. Severity set to 'normal' from 'important' Marked as found in versions linux/6.18.8-1 and linux/6.12.69-1. Added tag(s) confirmed and upstream. Merged 1130930 1131626 -- 1130930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1130930 1131626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1131626 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web