From: Bjorn Helgaas <helgaas@kernel.org>
To: Val Packett <val@packett.cool>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
linux-pci@vger.kernel.org, "Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-kernel@vger.kernel.org,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Guenter Roeck" <linux@roeck-us.net>,
regressions@lists.linux.dev
Subject: Re: [PATCH 1/2] PCI: Setup bridge resources earlier
Date: Thu, 30 Oct 2025 17:08:04 -0500 [thread overview]
Message-ID: <20251030220804.GA1655835@bhelgaas> (raw)
In-Reply-To: <20251028224758.GA1539235@bhelgaas>
On Tue, Oct 28, 2025 at 05:47:58PM -0500, Bjorn Helgaas wrote:
> On Mon, Oct 13, 2025 at 04:01:16PM -0500, Bjorn Helgaas wrote:
> > On Mon, Oct 06, 2025 at 05:00:25AM -0300, Val Packett wrote:
> > > On 9/24/25 10:42 AM, Ilpo Järvinen wrote:
> > > > Bridge windows are read twice from PCI Config Space, the first read is
> > > > made from pci_read_bridge_windows() which does not setup the device's
> > > > resources. It causes problems down the road as child resources of the
> > > > bridge cannot check whether they reside within the bridge window or
> > > > not.
> > > >
> > > > Setup the bridge windows already in pci_read_bridge_windows().
> > > >
> > > > Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > >
> > > Looks like this change has broken the WiFi (but not NVMe) on my Snapdragon
> > > X1E laptop (Latitude 7455):
> > ...
>
> > #regzbot introduced: a43ac325c7cb ("PCI: Set up bridge resources earlier")
> #regzbot fix: 469276c06aff ("PCI: Revert early bridge resource set up")
TIL that "#regzbot fix:" should include only the SHA1, not the commit
subject.
Also I think I should have used "#regzbot report:" to point to Val and
Guenter's original reports instead of "#regzbot introduced:".
#regzbot report: https://lore.kernel.org/r/017ff8df-511c-4da8-b3cf-edf2cb7f1a67@packett.cool
#regzbot report: https://lore.kernel.org/r/df266709-a9b3-4fd8-af3a-c22eb3c9523a@roeck-us.net
#regzbot fix: 469276c06aff
next prev parent reply other threads:[~2025-10-30 22:08 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 13:42 [PATCH 0/2] PCI: Fix bogus resource overlaps Ilpo Järvinen
2025-09-24 13:42 ` [PATCH 1/2] PCI: Setup bridge resources earlier Ilpo Järvinen
2025-10-06 8:00 ` Val Packett
2025-10-06 10:46 ` Ilpo Järvinen
2025-10-06 20:08 ` Val Packett
2025-10-07 15:43 ` Ilpo Järvinen
2025-10-09 7:29 ` Val Packett
2025-10-10 17:01 ` Ilpo Järvinen
2025-10-12 6:29 ` Val Packett
2025-10-16 7:42 ` Manivannan Sadhasivam
2025-10-13 21:01 ` Bjorn Helgaas
2025-10-28 22:47 ` Bjorn Helgaas
2025-10-30 22:08 ` Bjorn Helgaas [this message]
2025-10-13 18:07 ` Guenter Roeck
2025-10-14 11:20 ` Ilpo Järvinen
2025-10-17 18:22 ` Bhanu Seshu Kumar Valluri
2025-10-17 18:27 ` Bhanu Seshu Kumar Valluri
2025-10-17 18:52 ` Bjorn Helgaas
2025-10-18 1:57 ` Bhanu Seshu Kumar Valluri
2025-10-20 18:46 ` Ilpo Järvinen
2025-10-27 8:10 ` Bhanu Seshu Kumar Valluri
2025-10-27 13:49 ` Ilpo Järvinen
2025-09-24 13:42 ` [PATCH 2/2] PCI: Resources outside their window must set IORESOURCE_UNSET Ilpo Järvinen
2025-09-25 21:21 ` Bjorn Helgaas
2025-09-26 12:21 ` Ilpo Järvinen
2025-09-26 19:30 ` Bjorn Helgaas
2025-09-29 10:34 ` Ilpo Järvinen
2025-09-30 15:47 ` Geert Uytterhoeven
2025-09-30 16:32 ` Ilpo Järvinen
2025-10-01 11:49 ` Geert Uytterhoeven
2025-10-01 13:06 ` Ilpo Järvinen
2025-10-01 14:08 ` Geert Uytterhoeven
2025-10-02 14:54 ` Ilpo Järvinen
2025-10-02 15:25 ` Geert Uytterhoeven
2025-10-02 16:59 ` Ilpo Järvinen
2025-10-03 8:36 ` Geert Uytterhoeven
2025-10-03 14:58 ` Ilpo Järvinen
2025-10-06 10:14 ` Geert Uytterhoeven
2025-10-06 12:37 ` Ilpo Järvinen
2025-10-06 13:17 ` Geert Uytterhoeven
2025-10-07 17:30 ` Ilpo Järvinen
2025-10-08 8:40 ` Kai-Heng Feng
2025-10-08 13:57 ` Geert Uytterhoeven
2025-09-24 23:48 ` [PATCH 0/2] PCI: Fix bogus resource overlaps 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=20251030220804.GA1655835@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lucas.demarchi@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=regressions@lists.linux.dev \
--cc=val@packett.cool \
/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