public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
	linux-pm@vger.kernel.org, regressions@leemhuis.info
Subject: [bugzilla-daemon@kernel.org: [Bug 219765] New: Regression: VFIO NVIDIA GPU Passthrough Fails in Linux 6.13.0 (GPU Reset & Audio Controller Disappears)]
Date: Mon, 10 Feb 2025 11:07:15 -0600	[thread overview]
Message-ID: <20250210170715.GA8877@bhelgaas> (raw)

#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=219765

I don't see an obvious culprit between v6.12 and v6.13, suggested
bisection if possible.

Workaround: boot with pcie_port_pm=off

Given the workaround, maybe it's worth trying a revert of this:

  dc421bb3c0db ("PCI: Enable runtime PM of the host bridge")


----- Forwarded message from bugzilla-daemon@kernel.org -----

https://bugzilla.kernel.org/show_bug.cgi?id=219765

Created attachment 307599
  --> https://bugzilla.kernel.org/attachment.cgi?id=307599&action=edit
dmesg logs for the kernel in which gpu passthrough works

After upgrading from Linux 6.12.10 to Linux 6.13.0, VFIO GPU passthrough fails
for an NVIDIA GPU (AD107). The GPU is not passed through to the VM, and its
audio device (01:00.1) disappears from Virt-Manager. This issue does not occur
in Linux 6.12.10.

I have attached the logs.

             reply	other threads:[~2025-02-10 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 17:07 Bjorn Helgaas [this message]
2025-02-10 17:33 ` [bugzilla-daemon@kernel.org: [Bug 219765] New: Regression: VFIO NVIDIA GPU Passthrough Fails in Linux 6.13.0 (GPU Reset & Audio Controller Disappears)] Rafael J. Wysocki
2025-02-10 18:51   ` Rafael J. Wysocki
2025-02-11 18:47 ` Bjorn Helgaas

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=20250210170715.GA8877@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=alex.williamson@redhat.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    /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