From: kernel test robot <oliver.sang@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Jeff Layton <jlayton@kernel.org>, <linux-doc@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [fs] 313c47f4fe: BUG:kernel_hang_in_test_stage
Date: Tue, 27 Jan 2026 14:26:09 +0800 [thread overview]
Message-ID: <202601270735.29b7c33e-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "BUG:kernel_hang_in_test_stage" on:
commit: 313c47f4fe4d07eb2969f429a66ad331fe2b3b6f ("fs: use nullfs unconditionally as the real rootfs")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master ca3a02fda4da8e2c1cb6baee5d72352e9e2cfaea]
in testcase: trinity
version:
with following parameters:
runtime: 300s
group: group-00
nr_groups: 5
config: x86_64-kexec
compiler: clang-20
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G
(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/202601270735.29b7c33e-lkp@intel.com
[ 27.746952][ T1793] /lkp/lkp/src/monitors/meminfo: line 25: /lkp/lkp/src/bin/event/wait: not found
[ 31.757224][ T1793] /lkp/lkp/src/monitors/oom-killer: line 94: dmesg: not found
[ 31.757224][ T1793] /lkp/lkp/src/monitors/oom-killer: line 94: grep: not found
[ 31.757224][ T1793] /lkp/lkp/src/monitors/oom-killer: line 25: /lkp/lkp/src/bin/event/wait: not found
[ 65.744824][ T4974] trinity-main[4974]: segfault at 0 ip 0000000000000000 sp 00007ffe08d2ec08 error 15 likely on CPU 0 (core 0, socket 0)
[ 65.746308][ T4974] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Code starting with the faulting instruction
===========================================
/etc/rc5.d/S77lkp-bootstrap: line 79: sleep: not found
BUG: kernel hang in test stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260127/202601270735.29b7c33e-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-27 6:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 6:26 kernel test robot [this message]
2026-01-30 16:59 ` [linux-next:master] [fs] 313c47f4fe: BUG:kernel_hang_in_test_stage Christian Brauner
2026-01-31 11:41 ` Christian Brauner
2026-02-03 1:30 ` Oliver Sang
2026-02-03 12:57 ` Christian Brauner
2026-02-05 8:09 ` Oliver Sang
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=202601270735.29b7c33e-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@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