From: Neil Brown <neilb@suse.de>
To: Janos Haar <janos.haar@netcenter.hu>
Cc: linux-raid@vger.kernel.org
Subject: Re: RCU detected CPU 1 stall (t=4295904002/751 jiffies) Pid: 902, comm: md1_raid5
Date: Tue, 19 May 2009 11:05:54 +1000 [thread overview]
Message-ID: <18962.1522.937784.126331@notabene.brown> (raw)
In-Reply-To: message from Janos Haar on Tuesday May 19
On Tuesday May 19, janos.haar@netcenter.hu wrote:
> Hello list, Neil,
>
> Somebody can say something about this issue?
> I am not surprised, if it is hardware related, but this is on a brand new
> server, so i am looking for a solution... :-)
> May 17 23:12:13 gladiator-afth1 kernel: RCU detected CPU 1 stall
> (t=4295904002/751 jiffies)
I have no idea what this means.
I've occasionally seen this sort of message in early boot then the
system continued to work perfectly so I figured it was an early-boot
glitch. I suggest asking someone who understands RCU.
>
> The entire log is here:
> http://download.netcenter.hu/bughunt/20090518/messages
>
> The system is on the md1, and working, but slowly.
How slowly? Is the slowness due to disk throughput?
Have you tested the individual drives and compared that with the
array?
> If i left the server for 1 day, it will crash without a saved log.
This is a concern! It usually points to some sort of hardware
problem, but it is very hard to trace.
Is the power supply rated high enough to support all devices?
I cannot think of anything else to suggest .. except start swapping
components until the problem goes away...
NeilBrown
next prev parent reply other threads:[~2009-05-19 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 22:07 RCU detected CPU 1 stall (t=4295904002/751 jiffies) Pid: 902, comm: md1_raid5 Janos Haar
2009-05-19 1:05 ` Neil Brown [this message]
2009-05-19 10:30 ` Janos Haar
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=18962.1522.937784.126331@notabene.brown \
--to=neilb@suse.de \
--cc=janos.haar@netcenter.hu \
--cc=linux-raid@vger.kernel.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 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).