Linux block layer
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Genes Lists <lists@sapience.com>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvme@lists.infradead.org
Subject: Re: mainline boot fail nvme/block?
Date: Fri, 10 Oct 2025 08:54:46 -0600	[thread overview]
Message-ID: <cf4e88c6-0319-4084-8311-a7ca28a78c81@kernel.dk> (raw)
In-Reply-To: <4b392af8847cc19720ffcd53865f60ab3edc56b3.camel@sapience.com>

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.
> 
> It seems to get stuck enumerating disks within the initramfs created by
> dracut.
> 
> Subject to bisect verification, it may have started after commit
> 
>   e1b1d03ceec343362524318c076b110066ffe305
> 
>   Merge tag 'for-6.18/block-20250929' of 
>   git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux
> 
> Machine is dell xps 9320 laptop (firmware 2.23.0) with nvme
> partitioned:
> 
>     # lsblk -f
>     NAME        FSTYPE      FSVER LABEL FSAVAIL FSUSE% MOUNTPOINTS    
>     sr0
>     nvme0n1
>     ├─nvme0n1p1 vfat        FAT32 ESP   2.6G    12% /boot
>     ├─nvme0n1p2 ext4        1.0   root  77.7G    42% / 
>     └─nvme0n1p3 crypto_LUKS 2                          
>       └─home    btrfs             home  1.3T    26% /opt
>                                                     /home             
> 
> 
> 
> Will try do bisect over the weekend.

That'd be great, because there's really not much to glean from this bug
report.

-- 
Jens Axboe


  reply	other threads:[~2025-10-10 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10 14:29 mainline boot fail nvme/block? Genes Lists
2025-10-10 14:54 ` Jens Axboe [this message]
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

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=cf4e88c6-0319-4084-8311-a7ca28a78c81@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=lists@sapience.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