From: Oliver Sang <oliver.sang@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Shubhang Kaushik <shubhang@os.amperecomputing.com>,
<aubrey.li@linux.intel.com>, <yu.c.chen@intel.com>,
<oliver.sang@intel.com>
Subject: Re: [linus:master] [sched/fair] 4823725d9d: INFO:task_blocked_for_more_than#seconds
Date: Wed, 6 May 2026 16:09:02 +0800 [thread overview]
Message-ID: <afr3Hp/CgemmL3eY@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20260506074858.GB3126523@noisy.programming.kicks-ass.net>
hi, Peter Zijlstra,
On Wed, May 06, 2026 at 09:48:58AM +0200, Peter Zijlstra wrote:
> On Wed, May 06, 2026 at 03:06:13PM +0800, Oliver Sang wrote:
>
> > we tested upon below commit:
> > 0c0cf14be4909 (tip/sched/urgent) sched/fair: Fix wakeup_preempt_fair() for not waking up task
> >
> > found most issues are still existing
>
> Moo :-(
>
> > =========================================================================================
> > compiler/kconfig/rootfs/sleep/tbox_group/testcase:
> > gcc-14/i386-randconfig-2006-20250804/yocto-i386-minimal-20190520.cgz/1/vm-snb/boot
> >
> > 9fe89f022c05d99c 4823725d9d1d9cc5b36647e0cb8 0c0cf14be490975a7431e9d49fc
> > ---------------- --------------------------- ---------------------------
> > fail:runs %reproduction fail:runs %reproduction fail:runs
> > | | | | |
> > :499 13% 64:499 5% 23:1001 last_state.booting
> > :499 6% 29:499 3% 13:1001 dmesg.BUG:kernel_hang_in_boot_stage
> > :499 7% 33:499 2% 10:1001 dmesg.BUG:workqueue_lockup-pool
> > :499 0% 1:499 0% 1:1001 dmesg.EIP:_raw_spin_unlock_irqrestore
> > :499 1% 3:499 0% 1:1001 dmesg.EIP:finish_task_switch
> > :499 0% 1:499 0% :1001 dmesg.EIP:handle_softirqs
> > :499 0% 2:499 0% 1:1001 dmesg.EIP:lock_acquire
> > :499 0% 1:499 0% 2:1001 dmesg.EIP:lock_release
> > :499 0% 1:499 0% :1001 dmesg.EIP:on_each_cpu_cond_mask
> > :499 0% 1:499 0% :1001 dmesg.EIP:rcu_preempt_deferred_qs_irqrestore
> > :499 1% 3:499 0% 1:1001 dmesg.INFO:rcu_preempt_detected_stalls_on_CPUs/tasks
> > :499 3% 14:499 2% 10:1001 dmesg.INFO:task_blocked_for_more_than#seconds
> >
> > the config used for 0c0cf14be4909 is attached as config-7.1.0-rc1+
> > one dmesg from 0c0cf14be4909 for dmesg.INFO:task_blocked_for_more_than#seconds
> > is attached as dmesg-0c0cf14be4.decoded.xz
>
> Do you have a URL for that yocto image? git grep yocto on the lkp repo
> didn't immediately find me one, and I don't appear to have it in my
> .lkp/cache either.
it's here:
https://download.01.org/0day-ci/lkp-qemu/osimage/yocto/yocto-i386-minimal-20190520.cgz
>
next prev parent reply other threads:[~2026-05-06 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 13:19 [linus:master] [sched/fair] 4823725d9d: INFO:task_blocked_for_more_than#seconds kernel test robot
2026-05-05 15:29 ` Peter Zijlstra
2026-05-06 7:06 ` Oliver Sang
2026-05-06 7:48 ` Peter Zijlstra
2026-05-06 8:09 ` Oliver Sang [this message]
2026-05-06 8:23 ` Peter Zijlstra
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=afr3Hp/CgemmL3eY@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=shubhang@os.amperecomputing.com \
--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