From: kernel test robot <oliver.sang@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Oleg Nesterov <oleg@redhat.com>, <linux-kernel@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [clone] 4a34da4356: BUG:kernel_hang_in_boot_stage
Date: Mon, 16 Mar 2026 21:45:29 +0800 [thread overview]
Message-ID: <202603161449.201e2f5f-lkp@intel.com> (raw)
Hello,
we don't have enough knowledge to analyze the connection, but after rebuilding
kernel and rerun tests up to 100 times, the parent keeps clean, 4a34da4356
shows consistent boot issues.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/sleep:
vm-snb-i386/boot/yocto-i386-minimal-20190520.cgz/i386-randconfig-2006-20250804/gcc-14/1
ec93d3ee27d535ec 4a34da43569a1e0f7268e7dbd43
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:100 100% 100:100 last_state.booting
:100 97% 97:100 dmesg.BUG:kernel_hang_in_boot_stage
:100 3% 3:100 dmesg.BUG:workqueue_lockup-pool
:100 100% 100:100 dmesg.boot_failures
unfortunately, there is less information in dmesg. below report is just FTI.
kernel test robot noticed "BUG:kernel_hang_in_boot_stage" on:
commit: 4a34da43569a1e0f7268e7dbd435ad1eab5ff1b9 ("clone: add CLONE_NNP")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master f90aadf1c67c8b4969d1e5e6d4fd7227adb6e4d7]
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/202603161449.201e2f5f-lkp@intel.com
[ 0.289043][ T0] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.290216][ T0] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.291271][ T0] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.292235][ T0] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.293181][ T0] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
BUG: kernel hang in boot stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260316/202603161449.201e2f5f-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-16 13:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202603161449.201e2f5f-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oleg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.