From: Mario Limonciello <mario.limonciello@amd.com>
To: Cal Peake <cp@absolutedigital.net>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Mario Limonciello <superm1@kernel.org>,
Kent Russell <kent.russell@amd.com>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: amdgpu driver rebinding broken by "drm/amd: Clean up kfd node on surprise disconnect"
Date: Thu, 5 Feb 2026 11:48:34 -0600 [thread overview]
Message-ID: <eeef2b2e-6b64-43ec-924a-e4d0c9b9bba8@amd.com> (raw)
In-Reply-To: <b0c22deb-c0fa-3343-33cf-fd9a77d7db99@absolutedigital.net>
On 2/3/26 4:27 PM, Cal Peake wrote:
> Hi,
>
> The recent commit 28695ca09d32: "drm/amd: Clean up kfd node on surprise
> disconnect," has broken something with my VMs utilizing PCI passthrough.
> Before launching the VM, I unbind a secondary Radeon GPU from the amdgpu
> driver and then to the vfio-pci driver.
>
> Previously, everything would just work and I'd get the following kernel
> output:
>
> amdgpu 0000:14:00.0: amdgpu: amdgpu: finishing device.
> [drm] amdgpu: ttm finalized
> vfio-pci 0000:14:00.0: vgaarb: VGA decodes changed: olddecodes=none,decodes=io+mem:owns=none
> vfio-pci 0000:14:00.1: enabling device (0000 -> 0002)
> vfio-pci 0000:14:00.3: enabling device (0000 -> 0002)
>
> However, now when doing the rebinding: the host display (a different
> Radeon GPU) will freeze up and after a short time, the system will reset
> (thanks to a watchdog I believe) and I get this in the kernel log:
>
> amdgpu 0000:14:00.0: amdgpu: amdgpu: finishing device.
> vfio-pci 0000:14:00.1: Unable to change power state from D3hot to D0, device inaccessible
> vfio-pci 0000:14:00.3: Unable to change power state from D3hot to D0, device inaccessible
> vfio-pci 0000:14:00.2: Unable to change power state from D3hot to D0, device inaccessible
>
>
> Indeed, backing out the commit from kernels 6.12.67, 6.12.68, and 6.18.8
> gets things back to working.
>
> Please let me know if you have any ideas or if there is anymore debugging
> info I can provide.
>
> Thanks,
>
Here's a solution:
https://lore.kernel.org/amd-gfx/20260205164254.4091912-1-mario.limonciello@amd.com/
next prev parent reply other threads:[~2026-02-05 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 22:27 Cal Peake
2026-02-05 17:48 ` Mario Limonciello [this message]
2026-02-05 22:24 ` Cal Peake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eeef2b2e-6b64-43ec-924a-e4d0c9b9bba8@amd.com \
--to=mario.limonciello@amd.com \
--cc=alexander.deucher@amd.com \
--cc=cp@absolutedigital.net \
--cc=kent.russell@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=superm1@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®