Control: tags -1 + moreinfo Control: found -1 6.12.69-1 Hi Aman,
On Mon, Mar 16, 2026 at 01:12:21PM +0530, Aman wrote: > Package: src:linux > Version: 6.12.74-2 > Severity: normal > X-Debbugs-Cc: [email protected], [email protected] > User: [email protected] > Usertags: amd64 > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > Ans: The issue began after updating to kernel version 6.12.74+deb13+1-amd64. > During VM startup, the system fails or becomes stuck while trying to unload > the > AMD GPU driver, which is part of the script I use for single GPU passthrough. > My single GPU passthrough configuration and hook script work correctly with > kernel version 6.12.63+deb13-amd64, but the configuration stops working > starting from kernel version 6.12.69+deb13-amd64 up to the current version > 6.12.74+deb13+1-amd64. The problem appears to occur when the script attempts > to > unload the amdgpu driver. > > > * What exactly did you do (or not do) that was effective (or > ineffective)? > Ans: After updating the kernel to 6.12.74+deb13+1-amd64, my single GPU > passthrough configuration and hook script stopped working. I was unsure which > previous kernel version it had worked with, so I began installing and testing > older kernel versions. During testing, I found that the configuration and hook > script work correctly with kernel version 6.12.63+deb13-amd64 and earlier. > However, starting from kernel version 6.12.69+deb13-amd64 up to the current > 6.12.74+deb13+1-amd64, the single GPU passthrough configuration and hook > script > no longer work. For GPU passthrough, I am using SharkWipf, which requires hook > scripts. I will attach the script for reference. > > > * What was the outcome of this action? > Ans: After testing multiple kernel versions, I found that kernel versions > 6.12.69+deb13-amd64 up to the current 6.12.74+deb13+1-amd64 do not work with > my > single GPU passthrough configuration and hook script. I also tested two Trixie > backport kernels. With kernel version 6.18.15+deb13-amd64, the issue remained > the same and the configuration did not work. However, with kernel version > 6.17.13+deb13-amd64, the single GPU passthrough configuration and hook script > work correctly. Currently, I am using kernel 6.17.13+deb13-amd64 as a > workaround to avoid this problem. > > When I start the VM, I get a black screen, and no logs are generated > in > /var/log/libvirt/qemu/. Because of this, I suspected that the hook script > might > not be executing completely.To further investigate the issue, I connected via > SSH from a second computer to my main KVM host PC running kernel version > 6.12.74+deb13+1-amd64 and manually executed the hook script. The output was: > > ************************************************* > > sudo /etc/libvirt/hooks/qemu.d/Window11-Passthrough/prepare/begin/start.sh > [sudo] password for rv: > + systemctl stop display-manager.service > + echo 0 > + echo 0 > + modprobe -r amdgpu > > ************************************************** > > The hook script does not complete execution and appears to freeze while > attempting to unload the amdgpu module. While it is stuck at this step, the > system becomes unresponsive, and I am unable to cancel the execution with > Ctrl+C, which forces me to perform a hard reset of the PC. > > Please review this issue and consider fixing it in an upcoming kernel > update so that I can use the 6.12 kernel series on my KVM host PC. Currently, > my single GPU passthrough configuration works correctly with kernel version > 6.17.13+deb13-amd64, but it does not work with kernel versions > 6.12.69+deb13-amd64 through 6.12.74+deb13+1-amd64. Resolving this issue would > allow me to use the 6.12 kernel version without encountering the GPU > passthrough problem. As you have a relieable reproducer, would it be possible that tyou bisect the changes between 6.12.63 (good) and 6.12.69 (bad) to identify the breaking commit? (do you need instructions for that?) Regards, Salvatore
