From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Bernd Schumacher <bernd@bschu.de>, Lukas Wunner <lukas@wunner.de>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Mario Limonciello <mario.limonciello@amd.com>,
1131025@bugs.debian.org, regressions@lists.linux.dev,
stable@vger.kernel.org, linux-pci@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [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: Mon, 30 Mar 2026 16:56:24 +0300 (EEST) [thread overview]
Message-ID: <97b33e3d-1d95-5012-b599-717b95fa52e2@linux.intel.com> (raw)
In-Reply-To: <ecf9b2dd96ff97cc035ba297266b8dd05eea88da.camel@bschu.de>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Mon, 30 Mar 2026, Bernd Schumacher wrote:
> Am Sonntag, dem 29.03.2026 um 18:22 +0200 schrieb Lukas Wunner:
> > Could you repeat this and add log_buf_len=16M to the kernel command
> > line
> > so that the dmesg output isn't truncated?
>
> I have now added to /etc/default/grub:
> GRUB_CMDLINE_LINUX="\"dyndbg=file log_buf_len=16M drivers/pci/* +p\""
> attached is the dmesg result for 6.12.73
Hi,
This doesn't look like a resource assignment issue to me.
HOWEVER,
despite the assignment being successful, what is worth a note is that BAR
0 changes during resource fitting:
pci 0000:07:00.0: BAR 0 [mem 0xfffffffffc500000-0xfffffffffc50ffff 64bit]: can't claim; no compatible bridge window
pci 0000:07:00.0: BAR 0 [mem 0xfc500000-0xfc50ffff 64bit]: assigned
That is 0xffffffff -> 0x0 for the high order bits happens to match with
the change Lukas noted (I've not digged deeply into the logs beyond
checking the resource fitting/assignment results from the latest log).
Perhaps something on the save/restore side still holds the old value
despite the resource & BAR were changed during resource fitting?
--
i.
next prev parent reply other threads:[~2026-03-30 13:56 UTC|newest]
Thread overview: 29+ 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 [this message]
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
2026-03-28 14:40 ` Thorsten Leemhuis
2026-04-26 5:41 ` Lukas Wunner
2026-04-28 8:41 ` Thorsten Leemhuis
2026-04-28 9:58 ` Lukas Wunner
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=97b33e3d-1d95-5012-b599-717b95fa52e2@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=1131025@bugs.debian.org \
--cc=bernd@bschu.de \
--cc=bhelgaas@google.com \
--cc=carnil@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mario.limonciello@amd.com \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.