mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yuri Andriaccio <yurand2000@gmail.com>
To: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	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>
Cc: linux-kernel@vger.kernel.org,
	Luca Abeni <luca.abeni@santannapisa.it>,
	Yuri Andriaccio <yuri.andriaccio@santannapisa.it>
Subject: [BUG] Bw accounting warning on fair-servers' parameters change
Date: Fri, 18 Jul 2025 13:38:48 +0200	[thread overview]
Message-ID: <20250718113848.193139-1-yurand2000@gmail.com> (raw)

Hi,

I've been lately working on fair-servers and dl_servers for some patches and
I've come across a bandwidth accounting warning on the latest tip/master (as of
2025-07-18, git sha ed0272f0675f). The warning is triggered by simply starting
the machine, mounting debugfs and then just zeroing any fair-server's runtime.


The warning:

WARNING: kernel/sched/deadline.c:266 at dl_rq_change_utilization+0x208/0x230
static inline void __sub_rq_bw(u64 dl_bw, struct dl_rq *dl_rq) {
    ...
	WARN_ON_ONCE(dl_rq->running_bw > dl_rq->this_bw);
}

Steps to reproduce:

mount -t debugfs none /sys/kernel/debug
echo 0 > /sys/kernel/debug/sched/fair_server/cpu0/runtime


It does not happen at every machine boot, but happens on most. Could it possibly
be related to some of the deadline timers?

I'll probably follow up with some more tests to better understand what is going
on but I first wanted to bring this up.

Have a nice day,
Yuri

             reply	other threads:[~2025-07-18 11:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18 11:38 Yuri Andriaccio [this message]
2025-07-18 14:22 ` Juri Lelli
2025-07-18 14:53   ` Juri Lelli
2025-07-21  9:34     ` Yuri Andriaccio
2025-07-21 13:35       ` Juri Lelli

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=20250718113848.193139-1-yurand2000@gmail.com \
    --to=yurand2000@gmail.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@santannapisa.it \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=yuri.andriaccio@santannapisa.it \
    /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

all inboxes | Powered by JetHome®