From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: rcu_sched stall while waiting in csd_lock_wait()
Date: Wed, 2 Aug 2017 09:44:14 +0100 [thread overview]
Message-ID: <f0fa028b-b690-2b85-ca01-3642ff883e30@arm.com> (raw)
In-Reply-To: <20170802080827.GA15219@arm.com>
On 02/08/17 09:08, Will Deacon wrote:
> Hi Pratyush,
>
> On Wed, Aug 02, 2017 at 09:01:19AM +0530, Pratyush Anand wrote:
>> I am observing following rcu_sched stall while executing `perf record -a --
>> sleep 1` with one of the arm64 platform. It looks like that stalled cpu was
>> waiting in csd_lock_wait() from where it never came out,and so the stall.
>> Any help/pointer for further debugging would be very helpful. Problem also
>> reproduced with 4.13.0-rc3.
>
> When you say "also", which other kernel(s) show the problem? Is this a
> recent regression? Which platform are you running on?
>
> It would be interesting to know what the other CPUs are doing, in particular
> the target of the cross-call. Either it crashed spectacularly and didn't
> unlock the csd lock, or the IPI somehow wasn't delivered.
>
> Do you see any other splats if you enable lock debugging?
Also, is that in a guest, or bare metal? If that's a guest, what's the
host's kernel version?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <marc.zyngier@arm.com>
To: Will Deacon <will.deacon@arm.com>, Pratyush Anand <panand@redhat.com>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
mark.rutland@arm.com
Subject: Re: rcu_sched stall while waiting in csd_lock_wait()
Date: Wed, 2 Aug 2017 09:44:14 +0100 [thread overview]
Message-ID: <f0fa028b-b690-2b85-ca01-3642ff883e30@arm.com> (raw)
In-Reply-To: <20170802080827.GA15219@arm.com>
On 02/08/17 09:08, Will Deacon wrote:
> Hi Pratyush,
>
> On Wed, Aug 02, 2017 at 09:01:19AM +0530, Pratyush Anand wrote:
>> I am observing following rcu_sched stall while executing `perf record -a --
>> sleep 1` with one of the arm64 platform. It looks like that stalled cpu was
>> waiting in csd_lock_wait() from where it never came out,and so the stall.
>> Any help/pointer for further debugging would be very helpful. Problem also
>> reproduced with 4.13.0-rc3.
>
> When you say "also", which other kernel(s) show the problem? Is this a
> recent regression? Which platform are you running on?
>
> It would be interesting to know what the other CPUs are doing, in particular
> the target of the cross-call. Either it crashed spectacularly and didn't
> unlock the csd lock, or the IPI somehow wasn't delivered.
>
> Do you see any other splats if you enable lock debugging?
Also, is that in a guest, or bare metal? If that's a guest, what's the
host's kernel version?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2017-08-02 8:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 3:31 rcu_sched stall while waiting in csd_lock_wait() Pratyush Anand
2017-08-02 3:31 ` Pratyush Anand
2017-08-02 8:08 ` Will Deacon
2017-08-02 8:08 ` Will Deacon
2017-08-02 8:44 ` Marc Zyngier [this message]
2017-08-02 8:44 ` Marc Zyngier
2017-08-03 3:56 ` Pratyush Anand
2017-08-03 3:56 ` Pratyush Anand
2017-08-03 3:55 ` Pratyush Anand
2017-08-03 3:55 ` Pratyush Anand
2017-08-03 7:19 ` Marc Zyngier
2017-08-03 7:19 ` Marc Zyngier
2017-08-03 12:54 ` Paul E. McKenney
2017-08-03 12:54 ` Paul E. McKenney
2017-08-02 8:14 ` Peter Zijlstra
2017-08-02 8:14 ` Peter Zijlstra
2017-08-03 3:56 ` Pratyush Anand
2017-08-03 3:56 ` Pratyush Anand
2017-08-03 8:32 ` Peter Zijlstra
2017-08-03 8:32 ` Peter Zijlstra
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=f0fa028b-b690-2b85-ca01-3642ff883e30@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.