From: Bjorn Helgaas <helgaas@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Mark Brown <broonie@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-pci@vger.kernel.org,
"kernelci@groups.io" <kernelci@groups.io>,
"kernelci-results@groups.io" <kernelci-results@groups.io>
Subject: Re: next/master bisection: baseline.login on asus-C523NA-A20057-coral
Date: Tue, 5 Apr 2022 12:57:48 -0500 [thread overview]
Message-ID: <20220405175748.GA72007@bhelgaas> (raw)
In-Reply-To: <28ee7ff8-5b21-9154-74e9-efd59da4a498@collabora.com>
On Mon, Apr 04, 2022 at 08:44:41PM +0100, Guillaume Tucker wrote:
> On 29/03/2022 19:44, Guillaume Tucker wrote:
> > On 28/03/2022 13:54, Hans de Goede wrote:
> >> On 3/24/22 23:19, Mark Brown wrote:
> >>> On Thu, Mar 24, 2022 at 09:34:30PM +0100, Hans de Goede wrote:
> >> Ok, Guillaume, can you try a kernel with commit 5949965ec9340cfc0e65f7d8a576b660b26e2535
> >> ("x86/PCI: Preserve host bridge windows completely covered by E820") + the
> >> attached patch added on top a try on the asus-C523NA-A20057-coral machine please
> >> and see if that makes it boot again ?
> >
> > Sorry I've been busy with a conference. Sure, will put that
> > through KernelCI tomorrow and let you know the outcome.
>
> Well the issue seems to have been fixed on mainline, unless it's
> intermittent. In any case, next-20220404 is booting fine:
>
> https://linux.kernelci.org/test/plan/id/624aed811a5acd09adae071e/
>
> Last time it was seen to fail was next-20220330:
>
> https://linux.kernelci.org/test/plan/id/62442f68e30d6f89a4ae06b7/
This is because I dropped 5949965ec934 ("x86/PCI: Preserve host bridge
windows completely covered by E820") from the PCI tree starting with
next-20220401 because it causes the regression. So I expect
next-20220404 to boot fine (next-20220401 should boot fine as well; I
don't know whether that was tested).
The gory details:
20220330 should fail; it includes:
5949965ec934 ("x86/PCI: Preserve host bridge windows completely covered by E820")
d13f73e9108a ("x86/PCI: Log host bridge window clipping for E820 regions")
9c253994c5ba ("x86/PCI: Eliminate remove_e820_regions() common subexpressions")
ffb217a13a2e ("Linux 5.17-rc7")
20220331 should fail; it includes:
18146f25ac66 ("PCI: hv: Remove unused hv_set_msi_entry_from_desc()")
5949965ec934 ("x86/PCI: Preserve host bridge windows completely covered by E820")
d13f73e9108a ("x86/PCI: Log host bridge window clipping for E820 regions")
9c253994c5ba ("x86/PCI: Eliminate remove_e820_regions() common subexpressions")
ffb217a13a2e ("Linux 5.17-rc7")
20220401 should boot; it includes:
1c6cec4ab487 ("x86/PCI: Log host bridge window clipping for E820 regions")
b2922e67d233 ("x86/PCI: Eliminate remove_e820_regions() common subexpressions")
22ef7ee3eeb2 ("PCI: hv: Remove unused hv_set_msi_entry_from_desc()")
148a65047695 ("Merge tag 'pci-v5.18-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci")
20220404 should boot; it includes:
22ef7ee3eeb2 ("PCI: hv: Remove unused hv_set_msi_entry_from_desc()")
148a65047695 ("Merge tag 'pci-v5.18-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci")
> Ironically, the KernelCI staging linux-next job with the patches
> mentioned in your previous email applied is now failing:
>
> https://staging.kernelci.org/test/plan/id/624b2d3b923f532dc305f4c7/
This says we tested commit 1aceacc82d3f, which I guess is the
staging-next-20220404.1 tag at https://github.com/kernelci/linux.git.
It took me a while to find the commit history, but
https://github.com/kernelci/linux/commits/1aceacc82d3f says this
includes:
0a0c05a90278 x86/PCI: Limit "e820 entry fully covers window" check to non ISA MMIO
b5fd57109d22 x86/PCI: Preserve host bridge windows completely covered by E820
So the proposed fix (0a0c05a90278) apparently didn't work.
Bjorn
next prev parent reply other threads:[~2022-04-05 21:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <623c13ec.1c69fb81.8cbdb.5a7a@mx.google.com>
2022-03-24 17:52 ` next/master bisection: baseline.login on asus-C523NA-A20057-coral Mark Brown
2022-03-24 20:34 ` Hans de Goede
2022-03-24 22:19 ` Mark Brown
2022-03-28 12:54 ` Hans de Goede
2022-03-29 18:44 ` Guillaume Tucker
2022-04-04 19:44 ` Guillaume Tucker
2022-04-05 8:13 ` Hans de Goede
2022-04-05 17:57 ` Bjorn Helgaas [this message]
[not found] ` <16E2C910B4947F17.5433@groups.io>
2022-04-04 19:48 ` Guillaume Tucker
2022-03-30 11:35 ` Bjorn Helgaas
2022-04-04 8:45 ` Hans de Goede
2022-04-06 0:19 ` Bjorn Helgaas
2022-04-11 9:54 ` Hans de Goede
2022-04-11 9:57 ` Hans de Goede
2022-03-24 23:08 ` Bjorn Helgaas
2022-03-29 22:14 ` Bjorn Helgaas
2022-04-05 23:53 ` Bjorn Helgaas
2022-04-06 18:59 ` Bjorn Helgaas
2022-04-06 19:37 ` Mark Brown
2022-04-06 20:11 ` Guillaume Tucker
2022-04-07 15:17 ` Denys Fedoryshchenko
2022-04-06 20:56 ` Guenter Roeck
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=20220405175748.GA72007@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=guillaume.tucker@collabora.com \
--cc=hdegoede@redhat.com \
--cc=kernelci-results@groups.io \
--cc=kernelci@groups.io \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).