[<prev] [next>] [day] [month] [year] [list]
Message-ID: <202508071303.c1134cce-lkp@intel.com>
Date: Thu, 7 Aug 2025 13:39:32 +0800
From: kernel test robot <oliver.sang@...el.com>
To: Joel Fernandes <joelagnelf@...dia.com>
CC: <oe-lkp@...ts.linux.dev>, <lkp@...el.com>, <linux-kernel@...r.kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@...nel.org>, Xiongfeng Wang
<wangxiongfeng2@...wei.com>, Qi Xi <xiqi2@...wei.com>, "Paul E. McKenney"
<paulmck@...nel.org>, Linux Kernel Functional Testing <lkft@...aro.org>,
<rcu@...r.kernel.org>, <oliver.sang@...el.com>
Subject: [linus:master] [rcu] b41642c877: BUG:kernel_hang_in_boot_stage
Hello,
kernel test robot noticed "BUG:kernel_hang_in_boot_stage" on:
commit: b41642c87716bbd09797b1e4ea7d904f06c39b7b ("rcu: Fix rcu_read_unlock() deadloop due to IRQ work")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 7e161a991ea71e6ec526abc8f40c6852ebe3d946]
[test failed on linux-next/master 5c5a10f0be967a8950a2309ea965bae54251b50e]
in testcase: boot
config: i386-randconfig-2006-20250804
compiler: clang-20
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+-------------------------------+------------+------------+
| | d827673d8a | b41642c877 |
+-------------------------------+------------+------------+
| boot_successes | 15 | 0 |
| boot_failures | 0 | 15 |
| BUG:kernel_hang_in_boot_stage | 0 | 15 |
+-------------------------------+------------+------------+
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@...el.com>
| Closes: https://lore.kernel.org/oe-lkp/202508071303.c1134cce-lkp@intel.com
[ 8.004044][ T1] Run /init as init process
[ 8.004883][ T1] with arguments:
[ 8.005620][ T1] /init
[ 8.006332][ T1] with environment:
[ 8.007080][ T1] HOME=/
[ 8.007722][ T1] TERM=linux
[ 8.008407][ T1] RESULT_ROOT=/result/boot/1/vm-snb/quantal-i386-core-20190426.cgz/i386-randconfig-2006-20250804/clang-20/b41642c87716bbd09797b1e4ea7d904f06c39b7b/0
[ 8.010989][ T1] BOOT_IMAGE=/pkg/linux/i386-randconfig-2006-20250804/clang-20/b41642c87716bbd09797b1e4ea7d904f06c39b7b/vmlinuz-6.16.0-rc3-00005-gb41642c87716
[ 8.013525][ T1] branch=gustavoars/testing/wfamnae-next20250804
[ 8.014578][ T1] job=/lkp/jobs/scheduled/vm-meta-10/boot-1-quantal-i386-core-20190426.cgz-i386-randconfig-2006-20250804-b41642c87716-20250805-101381-u20lqt-1.yaml
[ 8.016412][ T1] user=lkp
[ 8.016884][ T1] ARCH=i386
[ 8.017372][ T1] kconfig=i386-randconfig-2006-20250804
[ 8.018109][ T1] commit=b41642c87716bbd09797b1e4ea7d904f06c39b7b
[ 8.018928][ T1] intremap=posted_msi
[ 8.019543][ T1] max_uptime=600
[ 8.020064][ T1] LKP_SERVER=internal-lkp-server
[ 8.020735][ T1] selinux=0
[ 8.021215][ T1] apic=debug
[ 8.021707][ T1] prompt_ramdisk=0
[ 8.022251][ T1] vga=normal
[ 8.022791][ T1] ia32_emulation=on
[ 8.023339][ T1] riscv_isa_fallback=1
[ 8.779434][ C0] random: crng init done
LKP: ttyS0: 107: skip deploy intel ucode as no ucode is specified
BUG: kernel hang in boot stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250807/202508071303.c1134cce-lkp@intel.com
we didn't observe more information in dmesg. and we only observe this "kernel
hang in boot stage" with a i386 random config. kernel is compiled by clang-20.
as a contrast, parent dmesg looks like below:
[ 8.301768][ T1] Run /init as init process
[ 8.302821][ T1] with arguments:
[ 8.303849][ T1] /init
[ 8.304408][ T1] with environment:
[ 8.305053][ T1] HOME=/
[ 8.305635][ T1] TERM=linux
[ 8.306225][ T1] RESULT_ROOT=/result/boot/1/vm-snb/quantal-i386-core-20190426.cgz/i386-randconfig-2006-20250804/clang-20/d827673d8a4e69937dd3731da2686a2d8206aef5/0
[ 8.308434][ T1] BOOT_IMAGE=/pkg/linux/i386-randconfig-2006-20250804/clang-20/d827673d8a4e69937dd3731da2686a2d8206aef5/vmlinuz-6.16.0-rc3-00004-gd827673d8a4e
[ 8.310619][ T1] branch=gustavoars/testing/wfamnae-next20250804
[ 8.311610][ T1] job=/lkp/jobs/scheduled/vm-meta-7/boot-1-quantal-i386-core-20190426.cgz-i386-randconfig-2006-20250804-d827673d8a4e-20250805-99925-p5h1vs-1.yaml
[ 8.313843][ T1] user=lkp
[ 8.314287][ T1] ARCH=i386
[ 8.314701][ T1] kconfig=i386-randconfig-2006-20250804
[ 8.315329][ T1] commit=d827673d8a4e69937dd3731da2686a2d8206aef5
[ 8.316029][ T1] intremap=posted_msi
[ 8.316574][ T1] max_uptime=600
[ 8.317018][ T1] LKP_SERVER=internal-lkp-server
[ 8.317599][ T1] selinux=0
[ 8.318009][ T1] apic=debug
[ 8.318424][ T1] prompt_ramdisk=0
[ 8.318888][ T1] vga=normal
[ 8.319307][ T1] ia32_emulation=on
[ 8.319841][ T1] riscv_isa_fallback=1
[ 9.079686][ C0] random: crng init done
LKP: ttyS0: 108: skip deploy intel ucode as no ucode is specified
[ 9.371040][ T182] udevd[182]: starting version 175
LKP: ttyS0: 108: Kernel tests: Boot OK!
LKP: ttyS0: 108: HOSTNAME vm-snb, MAC 52:54:00:12:34:56, kernel 6.16.0-rc3-00004-gd827673d8a4e 1
LKP: ttyS0: 108: /lkp/lkp/src/bin/run-lkp /lkp/jobs/scheduled/vm-meta-7/boot-1-quantal-i386-core-20190426.cgz-i386-randconfig-2006-20250804-d827673d8a4e-20250805-99925-p5h1vs-1.yaml
[ 10.016422][ T1] init: failsafe main process (327) killed by TERM signal
[ 10.080302][ T1] init: udev-fallback-graphics main process (366) terminated with status 1
[ 10.120853][ T1] init: networking main process (373) terminated with status 1
LKP: ttyS0: 108: LKP: rebooting forcely
[ 21.082808][ T108] sysrq: Emergency Sync
[ 21.084955][ T40] Emergency Sync complete
[ 21.086476][ T108] sysrq: Resetting
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Powered by blists - more mailing lists