From: kernel test robot <oliver.sang@intel.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [ast-bpf:stacklive_must_write] [bpf] 2b97edcbfd: BUG:kernel_hang_in_boot_stage
Date: Thu, 12 Mar 2026 16:30:09 +0800 [thread overview]
Message-ID: <202603121524.70171e6f-lkp@intel.com> (raw)
Hello,
sorry that we didn't capture more useful information in dmesg, but the results
looks quite persistent that 2b97edcbfd always crash early while parent seems be
able to run further. so we still make out this report FYI.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/sleep:
vm-snb-i386/boot/debian-11.1-i386-20220923.cgz/i386-randconfig-016-20260309/clang-20/1
305f3f033e1ec8a6 2b97edcbfd3d62b17ed04708448
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:50 100% 50:50 dmesg.BUG:kernel_hang_in_boot_stage
kernel test robot noticed "BUG:kernel_hang_in_boot_stage" on:
commit: 2b97edcbfd3d62b17ed04708448e140d681576f1 ("bpf: Resolve stack access from FP-derived pointers")
https://git.kernel.org/cgit/linux/kernel/git/ast/bpf.git stacklive_must_write
in testcase: boot
config: i386-randconfig-016-20260309
compiler: clang-20
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/202603121524.70171e6f-lkp@intel.com
[ 10.987909][ T1] IRQ13 -> 0:13
[ 10.988164][ T1] IRQ14 -> 0:14
[ 10.988418][ T1] IRQ15 -> 0:15
[ 10.988671][ T1] .................................... done.
[ 11.144010][ T1] sched_clock: Marking stable (11105621659, 38118780)->(11272634786, -128894347)
BUG: kernel hang in boot stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260312/202603121524.70171e6f-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-12 8:30 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=202603121524.70171e6f-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=ast@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