From: Thomas Gleixner <tglx@linutronix.de>
To: Abhishek Shah <abhishek.shah@broadcom.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
mingo@redhat.com, Peter Zijlstra <peterz@infradead.org>,
deepa.kernel@gmail.com, John Stultz <john.stultz@linaro.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Vikram Prakash <vikram.prakash@broadcom.com>
Subject: Re: timer-sp804: sched_clock: issue after first suspend
Date: Tue, 28 Nov 2017 17:43:33 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1711281742020.2222@nanos> (raw)
In-Reply-To: <CAKUFe6YJKEU8WiHWqAKOf20_c8XizVMFXr=12xO63kW9yrByuw@mail.gmail.com>
On Mon, 27 Nov 2017, Abhishek Shah wrote:
> Apart from this, I see following prints at times, can the above
> discussion be related to this behavior?
> [ 320.448348] INFO: rcu_sched detected stalls on CPUs/tasks:
> [ 320.454015] 3-...: (90 GPs behind) idle=162/140000000000001/0
> softirq=1220/1220 fqs=2462
> [ 320.462540] (detected by 1, t=5255 jiffies, g=518, c=517, q=37)
> [ 320.468738] Task dump for CPU 3:
> [ 320.472067] swapper/3 R running task 0 0 1 0x00000022
> [ 320.479341] Call trace:
> [ 320.481869] [<ffff000008085828>] __switch_to+0x98/0xb0
I dont think so. That's an issue which plagues Paul McKenney for quite some
time. It's either caused by a timer not firing or a wakeup being lost. We
have no idea yet how to debug that.
Thanks,
tglx
prev parent reply other threads:[~2017-11-28 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 11:32 Abhishek Shah
2017-11-28 16:43 ` Thomas Gleixner [this message]
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=alpine.DEB.2.20.1711281742020.2222@nanos \
--to=tglx@linutronix.de \
--cc=abhishek.shah@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel.lezcano@linaro.org \
--cc=deepa.kernel@gmail.com \
--cc=fweisbec@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vikram.prakash@broadcom.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®