On Wed, Oct 11, 2023 at 06:59:46AM +0530, Naresh Kamboju wrote: > Hi Steven and Greg, > > On Thu, 27 Apr 2023 at 15:19, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote: > > > > Hi Steven, > > > > On Wed, 26 Apr 2023 at 23:14, Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > > > > > On Wed, 26 Apr 2023 17:09:45 -0400 > > > Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > > > > > > Now the question is, why is this triggering on 4.19 but not in latest > > > > mainline? > > > > > > I found it, I backported this patch and the warning goes away (at least for > > > me). Can you add this and see if it makes the warning go away for you too? > > > > I have applied this patch on stable-rc 4.19 branch and tested on > > - arm64: Juno-r2 > > - x86_64 device > > > > and the reported problem has been resolved. > > > > Thanks for finding a quick fix patch. > > > > > > > > -- Steve > > > > > > From: Peter Zijlstra <peterz@xxxxxxxxxxxxx> > > > Date: Fri, 7 Aug 2020 20:50:19 +0200 > > > Subject: [PATCH] sched,idle,rcu: Push rcu_idle deeper into the idle path > > > > > > commit 1098582a0f6c4e8fd28da0a6305f9233d02c9c1d upstream. > > Can we expect this patch to be merged into 4.19 ? > The reason for the question is, the reported problem is still seen on > stable-rc 4.19. Ok, I'll queue it up now, I didn't realize it needed to be there, sorry. greg k-h
