[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251218101224.GN3707891@noisy.programming.kicks-ass.net>
Date: Thu, 18 Dec 2025 11:12:24 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Marek Szyprowski <m.szyprowski@...sung.com>
Cc: mingo@...nel.org, vincent.guittot@...aro.org,
linux-kernel@...r.kernel.org, juri.lelli@...hat.com,
dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
mgorman@...e.de, vschneid@...hat.com, tj@...nel.org,
void@...ifault.com, arighi@...dia.com, changwoo@...lia.com,
sched-ext@...ts.linux.dev, Heiko Stuebner <heiko@...ech.de>,
linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH 4/5] sched: Add assertions to QUEUE_CLASS
On Thu, Dec 18, 2025 at 11:09:13AM +0100, Marek Szyprowski wrote:
> On 27.11.2025 16:39, Peter Zijlstra wrote:
> > Add some checks to the sched_change pattern to validate assumptions
> > around changing classes.
> >
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
>
>
> This patch landed recently in linux-next as commit 47efe2ddccb1
> ("sched/core: Add assertions to QUEUE_CLASS"). In my tests it turned out
> that it triggers the following warning during simple 'rtcwake' test on
> Hardkernel's Odroid-M1 board
> (arch/arm64/boot/dts/rockchip/rk3568-odroid-m1.dts):
>
> root@...get:~# time rtcwake -s5 -mon
> rtcwake: wakeup using /dev/rtc0 at Thu Dec 18 10:01:28 2025
> ------------[ cut here ]------------
> WARNING: kernel/sched/core.c:10837 at sched_change_end+0x160/0x168,
https://lkml.kernel.org/r/176596899373.510.17191516261088315233.tip-bot2@tip-bot2
Powered by blists - more mailing lists