Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Kenneth Crudup <kenny@panix.com>
Cc: inochiama@gmail.com, tglx@linutronix.de, bhelgaas@google.com,
	unicorn_wang@outlook.com, linux-pci@vger.kernel.org,
	Genes Lists <lists@sapience.com>, Jens Axboe <axboe@kernel.dk>,
	Todd Brandt <todd.e.brandt@intel.com>
Subject: Re: commit 54f45a30c0 ("PCI/MSI: Add startup/shutdown for per device domains") causing boot hangs on my laptop
Date: Mon, 13 Oct 2025 16:18:15 -0500	[thread overview]
Message-ID: <20251013211815.GA864904@bhelgaas> (raw)
In-Reply-To: <af5f1790-c3b3-4f43-97d5-759d43e09c7b@panix.com>

[+cc Gene, Jens, Todd]

On Thu, Oct 02, 2025 at 10:04:17AM -0700, Kenneth Crudup wrote:
> 
> I'm running Linus' master (as of 7f7072574).
> 
> I bisected it to the above named commit (but had to back out ba9d484ed3
> (""PCI/MSI: Remove the conditional parent [un]mask logic") and then
> 727e914bbfbbd ("PCI/MSI: Check MSI_FLAG_PCI_MSI_MASK_PARENT in
> cond_[startup|shutdown]_parent()") first for a clean revert.)
> 
> I have a Dell XPS-9320 laptop, and booting would hang before it switched to
> the xe video driver from the EFI FB driver (not sure if this is a symptom or
> partial cause) and I'd see a message akin to "not being able to set up DP
> tunnels, destroying" as the last thing printed before it hangs. (If it's
> important to see those messages I believe I can force a pstore crash to get
> them where they can be saved off, let me know).

#regzbot introduced: 54f45a30c0 ("PCI/MSI: Add startup/shutdown for per device domains")
#regzbot link: https://lore.kernel.org/all/3152ca947e89ee37264b90c422e77bb0e3d575b9.camel@sapience.com/
#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=220658

  parent reply	other threads:[~2025-10-13 21:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 17:04 commit 54f45a30c0 ("PCI/MSI: Add startup/shutdown for per device domains") causing boot hangs on my laptop Kenneth Crudup
2025-10-02 22:28 ` Inochi Amaoto
2025-10-02 22:50   ` Kenneth Crudup
2025-10-02 23:37     ` Inochi Amaoto
2025-10-02 23:42       ` Kenneth Crudup
2025-10-02 23:45         ` Inochi Amaoto
2025-10-03  1:06           ` Kenneth Crudup
2025-10-13 21:18 ` Bjorn Helgaas [this message]
2025-10-13 21:19   ` Bjorn Helgaas
2025-10-28 22:52     ` Bjorn Helgaas
2025-10-30 22:27       ` Bjorn Helgaas
2025-10-14  0:13 ` Inochi Amaoto
2025-10-14  1:05   ` Kenneth Crudup
2025-10-14  3:10     ` Inochi Amaoto
     [not found] <lhrbiugb4o0da3rtcvl0aduk.1759451570558@email.android.com>
     [not found] ` <68df1c05.050a0220.31415.096bSMTPIN_ADDED_MISSING@mx.google.com>
2025-10-03  0:53   ` commit 54f45a30c0 ("PCI/MSI: Add startup/shutdown for per device? " Inochi Amaoto
2025-10-03  1:00     ` Kenneth Crudup
  -- strict thread matches above, loose matches on Subject: below --
2025-10-03  0:58 commit 54f45a30c0 ("PCI/MSI: Add startup/shutdown for per device " Kenneth Crudup
2025-10-03  1:06 ` Inochi Amaoto
2025-10-03  1:08   ` Kenneth Crudup
2025-10-03  1:10   ` Kenneth Crudup
2025-10-03  1:18     ` Inochi Amaoto
2025-10-03  1:30       ` Inochi Amaoto
2025-10-03  1:51         ` Kenneth Crudup
2025-10-03  2:03           ` Inochi Amaoto
2025-10-03  5:36             ` Kenneth Crudup
2025-10-03 12:01               ` Inochi Amaoto
2025-10-03 13:18                 ` Kenneth Crudup
2025-10-04  2:09                   ` Inochi Amaoto

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=20251013211815.GA864904@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bhelgaas@google.com \
    --cc=inochiama@gmail.com \
    --cc=kenny@panix.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lists@sapience.com \
    --cc=tglx@linutronix.de \
    --cc=todd.e.brandt@intel.com \
    --cc=unicorn_wang@outlook.com \
    /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