From: kernel test robot <oliver.sang@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Oleg Nesterov <oleg@redhat.com>,
<oliver.sang@intel.com>
Subject: [linus:master] [clone] 24baca56fa: dmesg.INFO:task_blocked_for_more_than#seconds
Date: Mon, 4 May 2026 16:08:17 +0800 [thread overview]
Message-ID: <202604301500.5a8b946c-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4528 bytes --]
Hello,
for this change, we reported
"[linux-next:master] [clone] 4a34da4356: BUG:kernel_hang_in_boot_stage"
in
https://lore.kernel.org/all/202603161449.201e2f5f-lkp@intel.com/
but at that time, we cannot supply more useful information.
since now the commit is in mainline, we made more tests.
we still observed BUG:kernel_hang_in_boot_stage issues we reported, and
we also found dmesg.BUG:workqueue_lockup-pool and
dmesg.INFO:task_blocked_for_more_than#seconds issues.
all these issues are clean on parent.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/sleep:
vm-snb-i386/boot/debian-11.1-i386-20220923.cgz/i386-randconfig-2006-20250804/gcc-14/1
12ae2c81b21cfaa1 24baca56fafc33d4fb77cd9858a
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:500 14% 70:500 dmesg.BUG:kernel_hang_in_boot_stage
:500 6% 31:500 dmesg.BUG:workqueue_lockup-pool
:500 12% 61:500 dmesg.INFO:task_blocked_for_more_than#seconds
since our bot failed to upload correct dmesg to [1], I attached one dmesg
for dmesg.INFO:task_blocked_for_more_than#seconds issue.
one further information is we only captured issue on this i386 randconfig,
we didn't see the issues from x86_64 configs so far.
if you want more informations, please kindly let us know. thanks a lot!
below is full report just FYI.
kernel test robot noticed "dmesg.INFO:task_blocked_for_more_than#seconds" on:
commit: 24baca56fafc33d4fb77cd9858a48c734183cb22 ("clone: add CLONE_NNP")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master dca922e019dd758b4c1b4bec8f1d509efddeaab4]
[test failed on linux-next/master 9974969c14031a097d6b45bcb7a06bb4aa525c40]
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/202604301500.5a8b946c-lkp@intel.com
(from attached dmesg)
[ 80.466242][ C0] random: crng init done
[ 110.868986][ C0] CE: hpet increased min_delta_ns to 56952 nsec
[ 983.071602][ T24] INFO: task kworker/u4:1:45 blocked for more than 491 seconds.
[ 983.269621][ T24] Not tainted 7.0.0-rc1+ #1
[ 983.271929][ T24] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 983.665248][ T24] task:kworker/u4:1 state:D stack:0 pid:45 tgid:45 ppid:25 task_flags:0x8040 flags:0x00080000
[ 983.673000][ T24] Call Trace:
[ 984.071216][ T24] __schedule+0x53e/0x590
[ 984.074774][ T24] ? sched_submit_work+0x61/0x80
[ 984.271098][ T24] schedule+0x39/0x50
[ 984.273895][ T24] async_synchronize_cookie_domain+0x9f/0x120
[ 984.568119][ T24] ? swake_up_all+0xa0/0xa0
[ 984.571275][ T24] wait_for_initramfs+0x43/0x50
[ 984.574087][ T24] call_usermodehelper_exec_async+0xb6/0xf0
[ 984.665708][ T24] ? umh_complete+0x20/0x20
[ 985.573782][ T24] ret_from_fork+0x1a/0x1e0
[ 985.973044][ T24] ? umh_complete+0x20/0x20
[ 986.173520][ T24] ret_from_fork_asm+0x12/0x20
[ 986.570161][ T24] entry_INT80_32+0x124/0x124
[ 986.672813][ T24]
[ 986.672813][ T24] Showing all locks held in the system:
[ 986.765370][ T24] 4 locks held by kworker/u4:0/12:
[ 986.769896][ T24] 1 lock held by khungtaskd/24:
[ 986.772774][ T24] #0: b22ac65c (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire+0x0/0x30
[ 986.973336][ T24] 2 locks held by kworker/u4:1/25:
[ 987.566505][ T24] #0: b30d18c0 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x196/0x3d0
[ 987.573333][ T24] #1: b33b1f18 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x1b9/0x3d0
[ 987.970427][ T24]
[ 987.974302][ T24] =============================================
[ 987.974302][ T24]
BUG: kernel hang in boot stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260430/202604301500.5a8b946c-lkp@intel.com [1]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[-- Attachment #2: dmesg.xz --]
[-- Type: application/x-xz, Size: 8896 bytes --]
reply other threads:[~2026-05-04 8:08 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=202604301500.5a8b946c-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox