From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: NTU <neotheuser@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: rcu_sched self-detected stall on CPU
Date: Thu, 15 Sep 2016 08:22:38 +0200 [thread overview]
Message-ID: <1473920558.8231.3.camel@gmail.com> (raw)
In-Reply-To: <CAM5Ud7NTrCV05SnVMv-EAg-LC3Rn3KigYM-yemB8_8G=Xq=Efw@mail.gmail.com>
On Wed, 2016-09-14 at 23:02 -0500, NTU wrote:
> [ 26.542980] Call Trace:
> [ 26.542983] [<ffffffffa7fbd7c1>] ? 0xffffffffa7fbd7c1
> [ 26.542985] [<ffffffffa7f17d35>] ? 0xffffffffa7f17d35
> [ 26.542986] [<ffffffffa796c115>] ? 0xffffffffa796c115
> [ 26.542988] [<ffffffffa7633d86>] ? 0xffffffffa7633d86
> [ 26.542989] [<ffffffffa796c0a6>] ? 0xffffffffa796c0a6
...
The stack trace is useless without symbols.
next prev parent reply other threads:[~2016-09-15 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 4:02 rcu_sched self-detected stall on CPU NTU
2016-09-15 6:22 ` Mike Galbraith [this message]
2016-09-15 17:15 ` NTU
2016-09-20 14:34 ` NTU
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=1473920558.8231.3.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neotheuser@gmail.com \
/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