From: Bjorn Helgaas <helgaas@kernel.org>
To: Genes Lists <lists@sapience.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-pci@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: mainline boot fail nvme/block? [BISECTED]
Date: Thu, 30 Oct 2025 17:23:22 -0500 [thread overview]
Message-ID: <20251030222322.GA1656973@bhelgaas> (raw)
In-Reply-To: <3152ca947e89ee37264b90c422e77bb0e3d575b9.camel@sapience.com>
On Fri, Oct 10, 2025 at 07:49:34PM -0400, Genes Lists wrote:
> On Fri, 2025-10-10 at 08:54 -0600, Jens Axboe wrote:
> > On 10/10/25 8:29 AM, Genes Lists wrote:
> > > Mainline fails to boot - 6.17.1 works fine.
> > > Same kernel on an older laptop without any nvme works just fine.
> ...
> Bisect landed here. (cc linux-pci@vger.kernel.org)
>
> 54f45a30c0d0153d2be091ba2d683ab6db6d1d5b is the first bad commit
> commit 54f45a30c0d0153d2be091ba2d683ab6db6d1d5b (HEAD)
> Author: Inochi Amaoto <inochiama@gmail.com>
> Date: Thu Aug 14 07:28:32 2025 +0800
>
> PCI/MSI: Add startup/shutdown for per device domains
#regzbot report: https://lore.kernel.org/r/4b392af8847cc19720ffcd53865f60ab3edc56b3.camel@sapience.com
#regzbot introduced: 54f45a30c0d0
#regzbot fix: e433110eb5bf
54f45a30c0d0 ("PCI/MSI: Add startup/shutdown for per device domains")
e433110eb5bf ("PCI: vmd: Override irq_startup()/irq_shutdown() in vmd_init_dev_msi_info()")
prev parent reply other threads:[~2025-10-30 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4b392af8847cc19720ffcd53865f60ab3edc56b3.camel@sapience.com>
[not found] ` <cf4e88c6-0319-4084-8311-a7ca28a78c81@kernel.dk>
2025-10-10 23:49 ` mainline boot fail nvme/block? [BISECTED] Genes Lists
2025-10-13 8:46 ` Inochi Amaoto
2025-10-13 11:45 ` Genes Lists
2025-10-14 0:54 ` Inochi Amaoto
2025-10-14 10:18 ` Genes Lists
2025-10-30 22:23 ` Bjorn Helgaas [this message]
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=20251030222322.GA1656973@bhelgaas \
--to=helgaas@kernel.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lists@sapience.com \
--cc=regressions@lists.linux.dev \
/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).