Hello,
this report is just FYI what we observed in our tests.
from commit message, it seems to us it should only impact arm or arm64,
however, we rebuild the kernel for this commit and parent several times,
rerun tests and the issues are quite persistent while parent keeps clean.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/runtime/test/torture_type:
vm-snb-i386/rcutorture/debian-11.1-i386-20220923.cgz/i386-randconfig-2006-20250804/gcc-14/300s/cpuhotplug/srcud
a594dec7607744a8 9f0cb91767f582df6b17c1e2f22
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:200 100% 200:200 last_state.booting
:200 100% 200:200 last_state.is_incomplete_run
:200 90% 179:200
dmesg.BUG:kernel_hang_in_boot_stage
:200 10% 21:200 dmesg.BUG:workqueue_lockup-pool
:200 2% 5:200 dmesg.EIP:_raw_spin_unlock_irq
:200 1% 2:200 dmesg.EIP:finish_task_switch
:200 0% 1:200 dmesg.EIP:get_recent_times
:200 2% 3:200 dmesg.EIP:lock_acquire
:200 0% 1:200 dmesg.EIP:lock_release
:200 0% 1:200 dmesg.EIP:preempt_schedule_irq
:200 1% 2:200
dmesg.EIP:rcu_preempt_deferred_qs_irqrestore
:200 100% 200:200 dmesg.boot_failures
the config used to build both commit/parent is uploaded to
https://download.01.org/0day-ci/archive/20251015/[email protected]/config-6.16.0-rc7-00008-g9f0cb91767f5
there is no CONFIG_HAVE_EXTRA_IPI_TRACEPOINTS.
though this really caused code difference between commit and parent while
compiling, we don't have enough knowledge how to connect to the issues.
another thing is most runs have dmesg.BUG:kernel_hang_in_boot_stage, which
has little hints in dmesg as below [1] which is uploaded by bot automatically
to
https://download.01.org/0day-ci/archive/20251015/[email protected]/dmesg.xz
we also noticed in some runs (~10%) there are issues of
"dmesg.BUG:workqueue_lockup-pool"
though still don't see the connection, attached one dmesg FYI
dmesg-9f0cb91767-workqueue_lockup-pool.xz
below is full report.
kernel test robot noticed "BUG:kernel_hang_in_boot_stage" on:
commit: 9f0cb91767f582df6b17c1e2f22f684c36962295 ("tracing: arm: arm64: Hide
trace events ipi_raise, ipi_entry and ipi_exit")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 0d97f2067c166eb495771fede9f7b73999c67f66]
[test failed on linux-next/master 68842969e138d9ad3e3aa2bbd65d514df1581b5c]
in testcase: rcutorture
version:
with following parameters:
runtime: 300s
test: cpuhotplug
torture_type: srcud
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 <[email protected]>
| Closes: https://lore.kernel.org/oe-lkp/[email protected]
[1]
[ 0.367885][ T0] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating
point registers'
[ 0.369051][ T0] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.370006][ T0] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.373610][ T0] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.378001][ 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/20251015/[email protected]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
dmesg-9f0cb91767-workqueue_lockup-pool.xz
Description: application/xz
