Linux-PCI Archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Herve Codina <herve.codina@bootlin.com>,
	Christian Zigotzky <chzigotzky@xenosoft.de>,
	Inochi Amaoto <inochiama@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org
Subject: PCI/MSI: Boot issue on X86 Laptop 6.18-rc1
Date: Wed, 15 Oct 2025 21:05:11 +0200	[thread overview]
Message-ID: <8d6887a5-60bc-423c-8f7a-87b4ab739f6a@hartkopp.net> (raw)

Hi all,

my Lenovo V17 Gen 2 (i7-1165G7) does not boot since commit

54f45a30c0d0 ("PCI/MSI: Add startup/shutdown for per device domains")

from the beginning of the 6.18 merge window.

I've checked the discussion about the original patch "[PATCH v2 2/4] 
PCI/MSI: Add startup/shutdown for per device domains" here:

https://lore.kernel.org/all/qe23hkpdr6ui4mgjke2wp2pl3jmgcauzgrdxqq4olgrkbfy25d@avy6c6mg334s/

where a fix has been suggested (which was later applied) that doesn't 
help on my machine. So the Linus' latest tree 
6.18.0-rc1-00017-g5a6f65d15025 still does not work.

I was pretty lost when trying to follow the PCI quirk discussion about 
"[PPC] Boot problems after the pci-v6.18-changes" here:

https://lore.kernel.org/linux-pci/4rtktpyqgvmpyvars3w3gvbny56y4bayw52vwjc3my3q2hw3ew@onz4v2p2uh5i/T/#ma4425fd40ec041dcda2393a55bca5907887c2b52

Any idea how I can support you to make my machine boot again?

Thanks,
Oliver

             reply	other threads:[~2025-10-15 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 19:05 Oliver Hartkopp [this message]
2025-10-15 22:24 ` PCI/MSI: Boot issue on X86 Laptop 6.18-rc1 Inochi Amaoto
2025-10-16  6:25   ` Oliver Hartkopp
2025-10-30 22:29 ` Bjorn Helgaas
2025-11-01  7:26   ` Oliver Hartkopp

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=8d6887a5-60bc-423c-8f7a-87b4ab739f6a@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=bhelgaas@google.com \
    --cc=chzigotzky@xenosoft.de \
    --cc=herve.codina@bootlin.com \
    --cc=inochiama@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).