LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Shrikanth Hegde <sshegde@linux.ibm.com>,
	jstultz@google.com, stultz@google.com
Subject: Re: [bisected][mainline]Kernel warnings at kernel/sched/cpudeadline.c:219
Date: Wed, 8 Oct 2025 11:50:39 +0200	[thread overview]
Message-ID: <20251008095039.GG3245006@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <8218e149-7718-4432-9312-f97297c352b9@linux.ibm.com>

On Wed, Oct 08, 2025 at 07:41:10AM +0530, Venkat Rao Bagalkote wrote:
> Greetings!!!
> 
> 
> IBM CI has reported a kernel warnings while running CPU hot plug operation
> on IBM Power9 system.
> 
> 
> Command to reproduce the issue:
> 
> drmgr -c cpu -r -q 1
> 
> 
> Git Bisect is pointing to below commit as the first bad commit.

Does something like this help?

(also, for future reference, please don't line wrap logs, it makes them
very hard to read)

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 198d2dd45f59..65f37bfcd661 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -8328,6 +8328,7 @@ static inline void sched_set_rq_offline(struct rq *rq, int cpu)
 		BUG_ON(!cpumask_test_cpu(cpu, rq->rd->span));
 		set_rq_offline(rq);
 	}
+	dl_server_stop(&rq->fair_server);
 	rq_unlock_irqrestore(rq, &rf);
 }
 


  reply	other threads:[~2025-10-08  9:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08  2:11 [bisected][mainline]Kernel warnings at kernel/sched/cpudeadline.c:219 Venkat Rao Bagalkote
2025-10-08  9:50 ` Peter Zijlstra [this message]
2025-10-08 10:17   ` Shrikanth Hegde
2025-10-08 11:13     ` Peter Zijlstra
2025-10-08 18:09       ` Shrikanth Hegde
2025-10-09  8:00         ` Peter Zijlstra
2025-10-09  9:47           ` Shrikanth Hegde
2025-10-09 11:49             ` Peter Zijlstra
2025-10-09 11:54           ` Marek Szyprowski

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=20251008095039.GG3245006@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=sshegde@linux.ibm.com \
    --cc=stultz@google.com \
    --cc=venkat88@linux.ibm.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