[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALjTZva=JHsckrBeHgJcd-_TDMgYgmZGcXavJ=GhPr7VQCOF5g@mail.gmail.com>
Date: Thu, 13 Apr 2023 16:32:32 +0100
From: Rui Salvaterra <rsalvaterra@...il.com>
To: paulmck@...nel.org
Cc: Jani Nikula <jani.nikula@...ux.intel.com>, rodrigo.vivi@...el.com,
tvrtko.ursulin@...ux.intel.com, intel-gfx@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [BUG?] INFO: rcu_sched detected expedited stalls on CPUs/tasks: {
0-.... } 3 jiffies s: 309 root: 0x1/.
Hi, Paul,
On Thu, 13 Apr 2023 at 15:43, Paul E. McKenney <paulmck@...nel.org> wrote:
>
> My guess would be that you have CONFIG_RCU_EXP_CPU_STALL_TIMEOUT set to
> some small non-zero number, for example, you might have set up a recent
> Android .config or some such. The default of zero would give you about
> 21 seconds rather than the three jiffies that you are seeing.
>
> Could you please check your .config?
Well, this is embarrassing. I can't fathom why/how, but I had it set
to 20, on this machine. That is, 20 millisseconds. I guess its a
miracle I haven't seen *more* expedited RCU traces. Sorry for the
noise, everyone.
Kind regards,
Rui
Powered by blists - more mailing lists