From: kernel test robot <oliver.sang@intel.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Christian Brauner <brauner@kernel.org>,
<linux-fsdevel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [fs] 51a146e059: BUG:kernel_hang_in_boot_stage
Date: Tue, 23 Dec 2025 10:36:19 +0800 [thread overview]
Message-ID: <202512230315.1717476b-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2328 bytes --]
Hello,
we don't have enough knowledge to analyze the connection between the issue and
this change. just observed the issue is quite persistent on 51a146e059 and
clean on its parent.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/sleep:
vm-snb-i386/boot/debian-11.1-i386-20220923.cgz/i386-randconfig-2006-20250804/gcc-14/1
d5bc4e31f2a3f301 51a146e0595c638c58097a1660f
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:200 100% 200:200 last_state.booting
:200 100% 200:200 last_state.is_incomplete_run
:200 100% 200:200 dmesg.BUG:kernel_hang_in_boot_stage
we cannot spot out useful information from dmesg which is uploaded to [1]. also
attached one dmesg from parent commit (d5bc4e31f2) FYI.
kernel test robot noticed "BUG:kernel_hang_in_boot_stage" on:
commit: 51a146e0595c638c58097a1660ff6b6e7d3b72f3 ("fs: Remove internal old mount API code")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master cc3aa43b44bdb43dfbac0fcb51c56594a11338a8]
in testcase: boot
config: i386-randconfig-2006-20250804
compiler: gcc-14
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202512230315.1717476b-lkp@intel.com
[ 15.178608][ T1] signal: max sigframe size: 1760
[ 15.669386][ T1] rcu: Hierarchical SRCU implementation.
[ 15.785114][ T1] rcu: Max phase no-delay instances is 1000.
[ 104.130757][ C0] workqueue: round-robin CPU selection forced, expect performance impact
[ 110.182304][ C0] random: crng init done
BUG: kernel hang in boot stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251223/202512230315.1717476b-lkp@intel.com [1]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[-- Attachment #2: dmesg-d5bc4e31f2.xz --]
[-- Type: application/x-xz, Size: 11712 bytes --]
next reply other threads:[~2025-12-23 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 2:36 kernel test robot [this message]
2025-12-26 20:01 ` [linux-next:master] [fs] 51a146e059: BUG:kernel_hang_in_boot_stage Eric Sandeen
2025-12-28 0:18 ` Eric Sandeen
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=202512230315.1717476b-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=sandeen@redhat.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