public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: "Alexandre N." <an.tech@mailo.com>
Cc: "Bernd Schumacher" <bernd@bschu.de>,
	"Uwe Kleine-König" <ukleinek@debian.org>,
	1131025@bugs.debian.org,
	"Salvatore Bonaccorso" <carnil@debian.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Mario Limonciello" <mario.limonciello@amd.com>,
	regressions@lists.linux.dev, stable@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Alex Williamson" <alex@shazbot.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: Bug#1131025: [6.12.y regression] Regression with 58130e7ce6cb ("PCI/ERR: Ensure error recoverability at all times"): echo vfio-pci >driver_override does not work for DVB Adapter
Date: Wed, 15 Apr 2026 18:05:14 +0200	[thread overview]
Message-ID: <ad-3OtA_i43_MmdU@wunner.de> (raw)
In-Reply-To: <6073a429-1932-456b-8cdf-29ba28f46a81@mailo.com>

On Wed, Apr 15, 2026 at 02:29:08AM +0200, Alexandre N. wrote:
> Please find attached the full dmesg with the debug patch
> and options you mentioned, using a clean 6.19.11 as a base.
> 
> This dmesg log shows a run with my host and guest issues (no
> disks from controller in VM, page fault error, virt-manager
> unresponsive etc).
> 0000:05:00.0 is the PCI SATA Controller device having issues.
> 
> Timings:
> - 36.447944: host ready after startup
> - 158.292119: VM starting
> - 166.564760: VM startup sequence ended
> - 286.631128: VM shutting down
> - 293.950976: VM shutdown sequence ended

Thank you!  In your case, the host kernel binds a driver to the
device which is unbound prior to passthrough.  Unbinding sets
current_state to PCI_UNKNOWN and that makes the problem re-appear
despite 4d4c10f763d7:

https://elixir.bootlin.com/linux/v6.19.11/source/drivers/pci/pci-driver.c#L484

On Bernd's system, the host kernel doesn't bind a driver to the
DVB adapter, hence 4d4c10f763d7 is sufficient to make the issue
disappear in his case.  I guess if he'd unbind vfio-pci and rebind
it, he'd see the problem again.

In any case, the patch is now submitted:

https://lore.kernel.org/r/febc3f354e0c1f5a9f5b3ee9ffddaa44caccf651.1776268054.git.lukas@wunner.de/

Thank you both for your efforts in reporting the bug and patiently
providing log output for debugging!

Lukas

  reply	other threads:[~2026-04-15 16:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <177373189751.7987.7156982489427825197.reportbug@obelix-trixie.bs.de>
2026-03-28 13:37 ` [6.12.y regression] Regression with 58130e7ce6cb ("PCI/ERR: Ensure error recoverability at all times"): echo vfio-pci >driver_override does not work for DVB Adapter Salvatore Bonaccorso
2026-03-28 14:11   ` Lukas Wunner
2026-03-28 16:16     ` Bernd Schumacher
2026-03-28 19:14       ` Lukas Wunner
2026-03-29 13:52         ` Bernd Schumacher
2026-03-29 16:22           ` Lukas Wunner
2026-03-30  6:14             ` Bernd Schumacher
2026-03-30 13:56               ` Ilpo Järvinen
2026-03-31 13:09               ` Lukas Wunner
2026-03-31 13:13                 ` Lukas Wunner
2026-03-31 23:01                 ` Alex Williamson
2026-04-01  4:11                   ` Lukas Wunner
2026-04-01 13:10               ` Bug#1131025: " Uwe Kleine-König
2026-04-01 16:16                 ` Bernd Schumacher
2026-04-01 20:18                   ` Lukas Wunner
2026-04-02  5:53                     ` Bernd Schumacher
2026-04-03 14:58                       ` Lukas Wunner
2026-04-04  9:54                         ` Bernd Schumacher
2026-04-12 18:04                           ` Alexandre N.
2026-04-13  3:40                             ` Lukas Wunner
2026-04-13  6:48                               ` Bernd Schumacher
2026-04-13 21:01                               ` Alexandre N.
2026-04-14  5:45                                 ` Lukas Wunner
2026-04-15  0:29                                   ` Alexandre N.
2026-04-15 16:05                                     ` Lukas Wunner [this message]
2026-03-28 14:40   ` Thorsten Leemhuis

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=ad-3OtA_i43_MmdU@wunner.de \
    --to=lukas@wunner.de \
    --cc=1131025@bugs.debian.org \
    --cc=alex@shazbot.org \
    --cc=an.tech@mailo.com \
    --cc=bernd@bschu.de \
    --cc=bhelgaas@google.com \
    --cc=carnil@debian.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=rafael@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=ukleinek@debian.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