From: kernel test robot <oliver.sang@intel.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>,
"Qais Yousef" <qyousef@layalina.io>, <linux-doc@vger.kernel.org>,
<aubrey.li@linux.intel.com>, <yu.c.chen@intel.com>,
<oliver.sang@intel.com>
Subject: [linus:master] [sched/pelt] 97450eb909: INFO:task_blocked_for_more_than#seconds
Date: Tue, 9 Jul 2024 15:22:29 +0800 [thread overview]
Message-ID: <202407091527.bb0be229-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "INFO:task_blocked_for_more_than#seconds" on:
commit: 97450eb909658573dcacc1063b06d3d08642c0c1 ("sched/pelt: Remove shift of thermal clock")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 22f902dfc51eb3602ff9b505ac3980f6ff77b1df]
[test failed on linux-next/master 0b58e108042b0ed28a71cd7edf5175999955b233]
in testcase: rcutorture
version:
with following parameters:
runtime: 300s
test: cpuhotplug
torture_type: tasks
compiler: gcc-13
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
we noticed the issue is random, 86 times out of 500 runs as below, while
keeping clean on parent.
d4dbc991714eefcb 97450eb909658573dcacc1063b0
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:500 17% 86:500 dmesg.INFO:task_blocked_for_more_than#seconds
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/202407091527.bb0be229-lkp@intel.com
[ 996.963402][ T17] INFO: task swapper:1 blocked for more than 491 seconds.
[ 996.973637][ T17] Tainted: G W 6.9.0-rc1-00051-g97450eb90965 #1
[ 996.983009][ T17] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 996.992369][ T17] task:swapper state:D stack:5680 pid:1 tgid:1 ppid:0 flags:0x00004000
[ 997.003585][ T17] Call Trace:
[ 997.022071][ T17] __schedule (kernel/sched/core.c:5412 kernel/sched/core.c:6746)
[ 997.032795][ T17] ? schedule (kernel/sched/core.c:6804 kernel/sched/core.c:6837)
[ 997.051350][ T17] schedule (arch/x86/include/asm/preempt.h:84 (discriminator 13) kernel/sched/core.c:6824 (discriminator 13) kernel/sched/core.c:6838 (discriminator 13))
[ 997.061394][ T17] async_synchronize_cookie_domain (kernel/async.c:317 (discriminator 9) kernel/async.c:310 (discriminator 9))
[ 997.071656][ T17] ? add_wait_queue (kernel/sched/wait.c:383)
[ 997.084201][ T17] wait_for_initramfs (init/initramfs.c:757)
[ 997.093158][ T17] ? do_header (init/initramfs.c:761)
[ 997.104204][ T17] populate_rootfs (init/initramfs.c:768)
[ 997.113736][ T17] do_one_initcall (init/main.c:1238)
[ 997.122668][ T17] ? parameq (kernel/params.c:90 (discriminator 1) kernel/params.c:99 (discriminator 1))
[ 997.133272][ T17] ? rdinit_setup (init/main.c:1286)
[ 997.142176][ T17] ? parse_args (kernel/params.c:142 (discriminator 1) kernel/params.c:186 (discriminator 1))
[ 997.172210][ T17] ? do_initcalls (init/main.c:1298 init/main.c:1316)
[ 997.183570][ T17] do_initcalls (init/main.c:1299 (discriminator 1) init/main.c:1316 (discriminator 1))
[ 997.194241][ T17] ? rest_init (init/main.c:1429)
[ 997.204290][ T17] kernel_init_freeable (init/main.c:1552)
[ 997.214432][ T17] kernel_init (init/main.c:1439)
[ 997.223979][ T17] ret_from_fork (arch/x86/kernel/process.c:153)
[ 997.232870][ T17] ? rest_init (init/main.c:1429)
[ 997.244227][ T17] ret_from_fork_asm (arch/x86/entry/entry_32.S:737)
[ 997.254412][ T17] entry_INT80_32 (arch/x86/entry/entry_32.S:944)
[ 997.831274][ T17]
[ 997.831274][ T17] Showing all locks held in the system:
[ 997.840770][ T17] 4 locks held by kworker/u4:1/16:
[ 997.844292][ T17] 1 lock held by khungtaskd/17:
[ 997.853205][ T17] #0: c26e50c8 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks (kernel/locking/lockdep.c:6612)
[ 997.880625][ T17]
[ 997.883881][ T17] =============================================
[ 997.883881][ T17]
BUG: kernel hang in boot stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240709/202407091527.bb0be229-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-07-09 7:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 7:22 kernel test robot [this message]
2024-07-09 10:03 ` [linus:master] [sched/pelt] 97450eb909: INFO:task_blocked_for_more_than#seconds Vincent Guittot
2024-07-12 16:41 ` Chen Yu
2024-07-24 11:34 ` Dietmar Eggemann
2024-07-24 15:09 ` Chen Yu
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=202407091527.bb0be229-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lukasz.luba@arm.com \
--cc=mingo@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=qyousef@layalina.io \
--cc=vincent.guittot@linaro.org \
--cc=yu.c.chen@intel.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