From: Steven Rostedt <rostedt@goodmis.org>
To: mitko@stz-bg.com
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Josh Triplett <josh@joshtriplett.org>,
linux-kernel@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: BUG: rcu_sched detected stalls on CPUs
Date: Fri, 20 Jan 2017 10:19:12 -0500 [thread overview]
Message-ID: <20170120101912.00498a6e@gandalf.local.home> (raw)
In-Reply-To: <a1ac66aa9e4f16f9779e3849cae3cc01@stz-bg.com>
On Fri, 20 Jan 2017 10:43:50 +0200
mitko@stz-bg.com wrote:
> [1.] One line summary of the problem:
>
> rcu_sched detected stalls on CPUs and few minutes server not respond.
Is this reproducible? Or was this a one time ordeal?
>
> [2.] Full description of the problem/report:
>
> Load of my server (postgres database) isnt big less then 0.50 and when
> error occured rcu_sched detected stalls on CPUs
> server freeze and nothing is work for 3-5 minute.
> No network, no video signal, no keyboard, no mouse. Nothing is worked.
> After these few minutes everything continue normal.
> This usual is happend once per day. When I check in google find a lots
> of ppl complain of this error, but no solution.
> Do any one know can help me to resolve it ? I spoke with few friends and
> they trying to convince me the problem is in CPU.
> I did not believe after a 3 years working CPU suddenly stop working
> correctly, but I might be wrong.
>
> [3.] Keywords (i.e., modules, networking, kernel):
>
> kernel
>
> [4.] Kernel information
> [4.1.] Kernel version (from /proc/version):
>
> Linux version 4.4.38 (root@hive64) (gcc version 5.4.0 (GCC) ) #2 SMP Sun
> Dec 11 16:11:02 CST 2016
>
Have you tried a newer version of the kernel?
-- Steve
next prev parent reply other threads:[~2017-01-20 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 8:43 BUG: rcu_sched detected stalls on CPUs mitko
2017-01-20 15:19 ` Steven Rostedt [this message]
2017-01-21 7:09 ` mitko
2017-05-08 6:43 ` mitko
2017-05-08 13:24 ` Paul E. McKenney
2017-05-08 15:01 ` Paul E. McKenney
2017-05-09 7:53 ` mitko
2017-05-09 14:49 ` Paul E. McKenney
2017-05-10 11:00 ` mitko
2017-05-10 14:32 ` Paul E. McKenney
2017-05-22 11:56 ` mitko
2017-05-22 13:07 ` Paul E. McKenney
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=20170120101912.00498a6e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mitko@stz-bg.com \
--cc=paulmck@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).