The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@redhat.com>
To: Marcel Ziswiler <marcel.ziswiler@codethink.co.uk>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Vineeth Pillai <vineeth@bitbyteword.org>,
	Luca Abeni <luca.abeni@santannapisa.it>
Subject: Re: SCHED_DEADLINE tasks causing WARNING at kernel/sched/sched.h message
Date: Thu, 4 Sep 2025 11:22:54 +0200	[thread overview]
Message-ID: <aLlabksolt1imHXe@jlelli-thinkpadt14gen4.remote.csb> (raw)
In-Reply-To: <7481bbd7c6652a963f132191dc622f1003938706.camel@codethink.co.uk>

Hi Marcel,

On 02/09/25 18:49, Marcel Ziswiler wrote:
> Hi
> 
> On Tue, 2025-09-02 at 16:06 +0200, Marcel Ziswiler wrote:
> > As part of our trustable work [1], we also run a lot of real time scheduler (SCHED_DEADLINE) tests on the
> > mainline Linux kernel (v6.16.2 in below reported case).
> 
> Looking through more logs from earlier test runs I found similar WARN_ONs dating back as early as v6.15.3. So
> it does not look like a "new" issue in that sense.
> 
> [snip]
> 
> Any help is much appreciated. Thanks!

What's the actual workload composition leading the warning. I noticed
stress-ng in the report. Could you please share more details?

Thanks!
Juri


  reply	other threads:[~2025-09-04  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 14:06 SCHED_DEADLINE tasks causing WARNING at kernel/sched/sched.h message Marcel Ziswiler
2025-09-02 16:49 ` Marcel Ziswiler
2025-09-04  9:22   ` Juri Lelli [this message]
2025-09-12 10:03     ` Marcel Ziswiler
2025-09-15 13:54       ` 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=aLlabksolt1imHXe@jlelli-thinkpadt14gen4.remote.csb \
    --to=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@santannapisa.it \
    --cc=marcel.ziswiler@codethink.co.uk \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=vineeth@bitbyteword.org \
    /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