Hi,
next release cycle, and another regression.
Yesterday after another kernel update in Fedora Rawhide system stopped booting.
Today thanks to git bisect, I found out that this is a commit:

❯ git bisect bad
a349d72fd9efc87c8fd1d16d3164752d84a7275b is the first bad commit
commit a349d72fd9efc87c8fd1d16d3164752d84a7275b
Author: Hugh Dickins <hughd@google.com>
Date:   Tue Jul 11 21:30:40 2023 -0700

    mm/pgtable: add rcu_read_lock() and rcu_read_unlock()s

    Patch series "mm: free retracted page table by RCU", v3.

    Some mmap_lock avoidance i.e.  latency reduction.  Initially just for the
    case of collapsing shmem or file pages to THPs: the usefulness of
    MADV_COLLAPSE on shmem is being limited by that mmap_write_lock it
    currently requires.

    Likely to be relied upon later in other contexts e.g.  freeing of empty
    page tables (but that's not work I'm doing).  mmap_write_lock avoidance
    when collapsing to anon THPs?  Perhaps, but again that's not work I've
    done: a quick attempt was not as easy as the shmem/file case.

    These changes (though of course not these exact patches) have been in
    Google's data centre kernel for three years now: we do rely upon them.


    This patch (of 13):

    Before putting them to use (several commits later), add rcu_read_lock() to
    pte_offset_map(), and rcu_read_unlock() to pte_unmap().  Make this a
    separate commit, since it risks exposing imbalances: prior commits have
    fixed all the known imbalances, but we may find some have been missed.

    Link: https://lkml.kernel.org/r/7cd843a9-aa80-14f-5eb2-33427363c20@google.com
    Link: https://lkml.kernel.org/r/d3b01da5-2a6-833c-6681-67a3e024a16f@google.com
    Signed-off-by: Hugh Dickins <hughd@google.com>
    Cc: Alexander Gordeev <agordeev@linux.ibm.com>
    Cc: Alistair Popple <apopple@nvidia.com>
    Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Anshuman Khandual <anshuman.khandual@arm.com>
    Cc: Axel Rasmussen <axelrasmussen@google.com>
    Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
    Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
    Cc: Christoph Hellwig <hch@infradead.org>
    Cc: Claudio Imbrenda <imbrenda@linux.ibm.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
    Cc: Heiko Carstens <hca@linux.ibm.com>
    Cc: Huang, Ying <ying.huang@intel.com>
    Cc: Ira Weiny <ira.weiny@intel.com>
    Cc: Jann Horn <jannh@google.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
    Cc: Lorenzo Stoakes <lstoakes@gmail.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Mel Gorman <mgorman@techsingularity.net>
    Cc: Miaohe Lin <linmiaohe@huawei.com>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Mike Rapoport (IBM) <rppt@kernel.org>
    Cc: Minchan Kim <minchan@kernel.org>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Pavel Tatashin <pasha.tatashin@soleen.com>
    Cc: Peter Xu <peterx@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Qi Zheng <zhengqi.arch@bytedance.com>
    Cc: Ralph Campbell <rcampbell@nvidia.com>
    Cc: Russell King <linux@armlinux.org.uk>
    Cc: SeongJae Park <sj@kernel.org>
    Cc: Song Liu <song@kernel.org>
    Cc: Steven Price <steven.price@arm.com>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Cc: Vasily Gorbik <gor@linux.ibm.com>
    Cc: Vishal Moola (Oracle) <vishal.moola@gmail.com>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Will Deacon <will@kernel.org>
    Cc: Yang Shi <shy828301@gmail.com>
    Cc: Yu Zhao <yuzhao@google.com>
    Cc: Zack Rusin <zackr@vmware.com>
    Cc: Zi Yan <ziy@nvidia.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

 include/linux/pgtable.h | 4 ++--
 mm/pgtable-generic.c    | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

It looks like the hang happens so early that when booting into a
working kernel and running "journalctl -b -1" I see in the console the
log of the previous kernel which was booted before the problematic
kernel.
Therefore, I apologize that I can't provide the kernel logs.
I can provides only photos when backtrace appears on my monitor:
Here we waiting: https://ibb.co/5xmm0BH
And then I see backtrace: https://ibb.co/TLLGFNP

Unfortunately I can't revert commit
a349d72fd9efc87c8fd1d16d3164752d84a7275b for testing more fresh builds
because of conflicts.

My hardware: https://linux-hardware.org/?probe=dd5735f315
I also attached kernel build config and full bisect log.

-- 
Best Regards,
Mike Gavrilov.