From: Peter Zijlstra <peterz@infradead.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: sched-ext@lists.linux.dev,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, Ingo Molnar <mingo@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Tejun Heo <tj@kernel.org>,
void@manifault.com, arighi@nvidia.com, changwoo@igalia.com
Subject: Re: Boot regression: arm64: WARNING: kernel/sched/core.c:10851 at sched_change_end
Date: Tue, 16 Dec 2025 13:21:27 +0100 [thread overview]
Message-ID: <20251216122127.GC3707891@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+G9fYuphjUO2x6qP2qPBFGSYz2WPp8fdGdiNGtyd1PmEVJrmQ@mail.gmail.com>
On Tue, Dec 16, 2025 at 05:09:52PM +0530, Naresh Kamboju wrote:
> The following boot warning is noticed on qemu-arm64 devices booting
> Linux next-20251215 on wards.
>
> Regression Analysis:
> - New regression? yes
> - Reproducibility? yes
>
> First seen on next-20251215
> Bad: next-20251215 and next-20251216
> Good: next-20251212
>
> Boot regression: arm64: WARNING: kernel/sched/core.c:10851 at sched_change_end
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
This is absolutely unreadable due to all the wrapping.
next prev parent reply other threads:[~2025-12-16 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 11:39 Boot regression: arm64: WARNING: kernel/sched/core.c:10851 at sched_change_end Naresh Kamboju
2025-12-16 12:21 ` Peter Zijlstra [this message]
2025-12-16 17:23 ` Mark Rutland
2025-12-16 19:11 ` Naresh Kamboju
2025-12-17 12:04 ` Mark Rutland
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=20251216122127.GC3707891@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arighi@nvidia.com \
--cc=bsegall@google.com \
--cc=changwoo@igalia.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=rostedt@goodmis.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=void@manifault.com \
--cc=vschneid@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