From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <oliver.sang@intel.com>
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
Subject: Re: [linus:master] [sched/fair] 4823725d9d: INFO:task_blocked_for_more_than#seconds
Date: Tue, 5 May 2026 17:29:18 +0200 [thread overview]
Message-ID: <20260505152918.GY3126523@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <202605052050.8156b7e0-lkp@intel.com>
On Tue, May 05, 2026 at 09:19:49PM +0800, kernel test robot wrote:
>
>
> Hello,
>
>
> for this change "sched/fair: Increase weight bits for avg_vruntime", we reported
> "[peterz-queue:sched/hrtick] [sched/fair] fb047eb995: Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]KASAN_PTI"
> in [1]
>
> but we cannot reproduce the issue in [1] now with same tests and the same
> x86_64-randconfig as the kbuild input config for 4823725d9d.
>
> however, with another i386-randconfig in boot tests, we found some random
> issues for this change which are clean on parent.
Much of that branch has since made its way upstream -- with various bugs
fixed. Can any of this be reproduced on tip/sched/urgent ?
next prev parent reply other threads:[~2026-05-05 15:29 UTC|newest]
Thread overview: 5+ 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 [this message]
2026-05-06 7:06 ` Oliver Sang
2026-05-06 7:48 ` Peter Zijlstra
2026-05-06 8:09 ` Oliver Sang
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=20260505152918.GY3126523@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=oliver.sang@intel.com \
--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