From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: "Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Hans de Goede <hdegoede@redhat.com>,
Thorsten Leemhuis <regressions@leemhuis.info>,
linux-kernel@vger.kernel.org
Subject: [bugzilla-daemon@kernel.org: [Bug 216109] New: Steam Deck fails to boot when E820 entries clipped out of _CRS]
Date: Thu, 9 Jun 2022 17:43:39 -0500 [thread overview]
Message-ID: <20220609224339.GA543225@bhelgaas> (raw)
New regression in v5.19-rc1.
----- Forwarded message from bugzilla-daemon@kernel.org -----
Subject: [Bug 216109] New: Steam Deck fails to boot when E820 entries clipped
out of _CRS
https://bugzilla.kernel.org/show_bug.cgi?id=216109
Summary: Steam Deck fails to boot when E820 entries clipped out
of _CRS
Kernel Version: v5.19
Guilherme G. Piccoli reported that v5.18 boots fine on Steam Deck, but
v5.19-rc1 does not. He bisected it to 4c5e242d3e93 ("x86/PCI: Clip only host
bridge windows for E820 regions") [1].
A quirk similar to [2] that disables E820 clipping makes v5.19-rc1 work again.
The reason why v5.18 (which always does E820 clipping by default) works, while
v5.19-rc1 (which also does E820 clipping on this platform) does not has not
been explained yet.
[1] https://git.kernel.org/linus/4c5e242d3e93
[2] https://git.kernel.org/linus/d341838d776a
----- End forwarded message -----
next reply other threads:[~2022-06-09 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 22:43 Bjorn Helgaas [this message]
2022-06-10 11:14 ` [bugzilla-daemon@kernel.org: [Bug 216109] New: Steam Deck fails to boot when E820 entries clipped out of _CRS] Hans de Goede
2022-06-12 11:11 ` Thorsten Leemhuis
2022-06-19 12:37 ` [bugzilla-daemon@kernel.org: [Bug 216109] New: Steam Deck fails to boot when E820 entries clipped out of _CRS] #forregzbot 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=20220609224339.GA543225@bhelgaas \
--to=helgaas@kernel.org \
--cc=gpiccoli@igalia.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).