From: kernel test robot <oliver.sang@intel.com>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [jfern:tick/keep-tick-on-hrt] [sched/core] e7e6035c3d: WARNING:at_kernel/sched/deadline.c:#__pick_next_task_dl
Date: Wed, 28 Feb 2024 09:46:41 +0800 [thread overview]
Message-ID: <202402271655.48b83635-lkp@intel.com> (raw)
Hello,
we noticed the parent also has a similar WARNING, which just changed to
'WARNING:at_kernel/sched/deadline.c:#__pick_next_task_dl' due to code change.
however, due to limitation of our auto-bisect flow, it's hard for us to
find out which commit caused
'WARNING:at_kernel/sched/deadline.c:#pick_task_dl'
we just report this FYI that we observed the WARNING shows in our tests, which
happens in a random way (as below, 2 times out of 8 runs for e7e6035c3d and its
parent).
272ad52e410abe39 e7e6035c3d861787cba5c333a45
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:8 25% 2:8 dmesg.EIP:__pick_next_task_dl
2:8 -25% :8 dmesg.EIP:pick_task_dl
:8 25% 2:8 dmesg.WARNING:at_kernel/sched/deadline.c:#__pick_next_task_dl
2:8 -25% :8 dmesg.WARNING:at_kernel/sched/deadline.c:#pick_task_dl
below is details.
kernel test robot noticed "WARNING:at_kernel/sched/deadline.c:#enqueue_dl_entity" on:
commit: e7e6035c3d861787cba5c333a457b6c651efe6ab ("sched/core: Fix picking of tasks for core scheduling with DL server")
https://git.kernel.org/cgit/linux/kernel/git/jfern/linux.git tick/keep-tick-on-hrt
in testcase: boot
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(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/202402271655.48b83635-lkp@intel.com
[ 24.478616][ T38] ------------[ cut here ]------------
[ 24.479061][ T38] WARNING: CPU: 1 PID: 38 at kernel/sched/deadline.c:2300 __pick_next_task_dl+0x26/0xac
[ 24.479755][ T38] Modules linked in:
[ 24.480034][ T38] CPU: 1 PID: 38 Comm: kworker/1:1 Tainted: G W 6.8.0-rc4-00023-ge7e6035c3d86 #1
[ 24.480765][ T38] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 24.481492][ T38] Workqueue: 0x0 (events_power_efficient)
[ 24.481902][ T38] EIP: __pick_next_task_dl+0x26/0xac
[ 24.482274][ T38] Code: 58 5a eb d0 8b 88 58 05 00 00 85 c9 0f 84 98 00 00 00 55 89 e5 57 89 d7 56 89 c6 53 eb 2b 66 90 ff 93 a8 00 00 00 85 c0 75 41 <0f> 0b 80 4b 48 02 89 da 89 f0 6a 00 6a 00 e8 ff fc ff ff 8b 8e 58
[ 24.482538][ T38] EAX: 00000000 EBX: ea883a60 ECX: 00000003 EDX: 00000000
[ 24.482538][ T38] ESI: ea8834c0 EDI: 00000000 EBP: c4643ee8 ESP: c4643edc
[ 24.482538][ T38] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010046
[ 24.482538][ T38] CR0: 80050033 CR2: 00000000 CR3: 037ea000 CR4: 000406d0
[ 24.482538][ T38] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[ 24.482538][ T38] DR6: fffe0ff0 DR7: 00000400
[ 24.482538][ T38] Call Trace:
[ 24.482538][ T38] ? show_regs+0x70/0x78
[ 24.482538][ T38] ? __pick_next_task_dl+0x26/0xac
[ 24.482538][ T38] ? __warn+0x6f/0x16c
[ 24.482538][ T38] ? __pick_next_task_dl+0x26/0xac
[ 24.482538][ T38] ? report_bug+0x170/0x194
[ 24.482538][ T38] ? exc_overflow+0x38/0x38
[ 24.482538][ T38] ? handle_bug+0x2a/0x48
[ 24.482538][ T38] ? exc_invalid_op+0x25/0x64
[ 24.482538][ T38] ? handle_exception+0x133/0x133
[ 24.482538][ T38] ? exc_overflow+0x38/0x38
[ 24.482538][ T38] ? __pick_next_task_dl+0x26/0xac
[ 24.482538][ T38] ? exc_overflow+0x38/0x38
[ 24.482538][ T38] ? __pick_next_task_dl+0x26/0xac
[ 24.482538][ T38] pick_next_task_dl+0xe/0x3c
[ 24.482538][ T38] __schedule+0x50c/0x83c
[ 24.482538][ T38] ? schedule+0x9e/0xd8
[ 24.482538][ T38] schedule+0x3a/0xd8
[ 24.482538][ T38] worker_thread+0x169/0x394
[ 24.482538][ T38] kthread+0xd0/0xf8
[ 24.482538][ T38] ? rescuer_thread+0x2e4/0x2e4
[ 24.482538][ T38] ? kthread_complete_and_exit+0x18/0x18
[ 24.482538][ T38] ret_from_fork+0x29/0x40
[ 24.482538][ T38] ? kthread_complete_and_exit+0x18/0x18
[ 24.482538][ T38] ret_from_fork_asm+0x12/0x18
[ 24.482538][ T38] entry_INT80_32+0x125/0x125
[ 24.482538][ T38] irq event stamp: 26398
[ 24.482538][ T38] hardirqs last enabled at (26397): [<c231ac8d>] _raw_spin_unlock_irq+0x1d/0x3c
[ 24.482538][ T38] hardirqs last disabled at (26398): [<c2310af5>] __schedule+0x3dd/0x83c
[ 24.482538][ T38] softirqs last enabled at (26394): [<c1fcefa3>] neigh_managed_work+0x9f/0xa8
[ 24.482538][ T38] softirqs last disabled at (26390): [<c1fcef22>] neigh_managed_work+0x1e/0xa8
[ 24.482538][ T38] ---[ end trace 0000000000000000 ]---
[ 63.158742][ C0] BUG: workqueue lockup - pool cpus=0-1 node=0 flags=0x4 nice=0 stuck for 38s!
[ 63.160422][ C0] Showing busy workqueues and worker pools:
[ 63.161383][ C0] workqueue events_unbound: flags=0x2
[ 63.162263][ C0] pwq 6: cpus=0-1 node=0 flags=0x4 nice=0 active=1/512 refcnt=2
[ 63.162273][ C0] pending: flush_memcg_stats_dwork
BUG: kernel hang in boot stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240227/202402271655.48b83635-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-28 1:46 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=202402271655.48b83635-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=joel@joelfernandes.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).