Messages in this thread | | | Subject | Re: [linux-next] cpus stalls detected few hours after booting next kernel | From | Abdul Haleem <> | Date | Tue, 25 Jul 2017 10:49:57 +0530 |
| |
On Fri, 2017-06-30 at 17:28 +1000, Nicholas Piggin wrote: > On Fri, 30 Jun 2017 10:52:18 +0530 > Abdul Haleem <abdhalee@linux.vnet.ibm.com> wrote: > > > On Fri, 2017-06-30 at 00:45 +1000, Nicholas Piggin wrote: > > > On Thu, 29 Jun 2017 20:23:05 +1000 > > > Nicholas Piggin <npiggin@gmail.com> wrote: > > > > > > > On Thu, 29 Jun 2017 19:36:14 +1000 > > > > Nicholas Piggin <npiggin@gmail.com> wrote: > > > > > > > > I don't *think* the replay-wakeup-interrupt patch is directly involved, but > > > > > it's likely to be one of the idle patches. > > > > > > Okay this turned out to be misconfigured sleep states I added for the > > > simulator, sorry for the false alarm. > > > > > > > Although you have this in the backtrace. I wonder if that's a stuck > > > > lock in rcu_process_callbacks? > > > > > > So this spinlock becomes top of the list of suspects. Can you try > > > enabling lockdep and try to reproduce it? > > > > Yes, recreated again with CONFIG_LOCKDEP=y & CONFIG_DEBUG_LOCKDEP=y set. > > I do not see any difference in trace messages with and without LOCKDEP > > enabled. > > > > Please find the attached log file. > > Can you get an rcu_invoke_callback event trace that Paul suggested?
Yes, I have collected the perf report. > > Does this bug show up with just the powerpc next branch?
Now started seeing the call trace on mainline too (4.13.0-rc2)
> > Thanks, > Nick >
-- Regard's
Abdul Haleem IBM Linux Technology Centre
| |