From: "Janos Haar" <janos.haar@netcenter.hu>
To: linux-raid@vger.kernel.org
Subject: RCU detected CPU 1 stall (t=4295904002/751 jiffies) Pid: 902, comm: md1_raid5
Date: Tue, 19 May 2009 00:07:40 +0200 [thread overview]
Message-ID: <12a901c9d805$119fef20$0400a8c0@dcccs> (raw)
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)
May 17 23:12:13 gladiator-afth1 kernel: Pid: 902, comm: md1_raid5 Not
tainted 2.6.28.10 #1
May 17 23:12:13 gladiator-afth1 kernel: Call Trace:
May 17 23:12:13 gladiator-afth1 kernel: <IRQ> [<ffffffff80265395>] ?
get_timestamp+0x9/0xf
May 17 23:12:13 gladiator-afth1 kernel: [<ffffffff8026854f>]
__rcu_pending+0x64/0x1e2
May 17 23:12:13 gladiator-afth1 kernel: [<ffffffff80268703>]
rcu_pending+0x36/0x6f
May 17 23:12:13 gladiator-afth1 kernel: [<ffffffff8023f546>]
update_process_times+0x37/0x5f
May 17 23:12:13 gladiator-afth1 kernel: [<ffffffff802504a7>]
tick_periodic+0x6e/0x7a
May 17 23:12:13 gladiator-afth1 kernel: [<ffffffff802504d4>]
tick_handle_periodic+0x21/0x65
May 17 23:12:13 gladiator-afth1 kernel: [<ffffffff8021ad60>]
smp_apic_timer_interrupt+0x8f/0xad
May 17 23:12:13 gladiator-afth1 kernel: [<ffffffff8020bf1b>]
apic_timer_interrupt+0x6b/0x70
May 17 23:12:13 gladiator-afth1 kernel: <EOI> [<ffffffff80820b8f>] ?
_spin_unlock_irqrestore+0x13/0x17
May 17 23:12:13 gladiator-afth1 kernel: [<ffffffff80728720>] ?
bitmap_daemon_work+0x142/0x3b0
May 17 23:12:18 gladiator-afth1 kernel: [<ffffffff80724c58>] ?
md_check_recovery+0x1b/0x45b
May 17 23:12:18 gladiator-afth1 kernel: [<ffffffff8071976c>] ?
raid5d+0x5d/0x503
May 17 23:12:18 gladiator-afth1 kernel: [<ffffffff80726533>] ?
md_thread+0xd5/0xed
May 17 23:12:18 gladiator-afth1 kernel: [<ffffffff80248e4a>] ?
autoremove_wake_function+0x0/0x38
May 17 23:12:18 gladiator-afth1 kernel: [<ffffffff8072645e>] ?
md_thread+0x0/0xed
May 17 23:12:18 gladiator-afth1 kernel: [<ffffffff80248d3b>] ?
kthread+0x49/0x76
May 17 23:12:18 gladiator-afth1 kernel: [<ffffffff8020c169>] ?
child_rip+0xa/0x11
May 17 23:12:18 gladiator-afth1 kernel: [<ffffffff80248cf2>] ?
kthread+0x0/0x76
May 17 23:12:18 gladiator-afth1 kernel: [<ffffffff8020c15f>] ?
child_rip+0x0/0x11
The entire log is here:
http://download.netcenter.hu/bughunt/20090518/messages
The system is on the md1, and working, but slowly.
If i left the server for 1 day, it will crash without a saved log.
Memtest survived >48 hour.
Thanks,
Janos Haar
next reply other threads:[~2009-05-18 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 22:07 Janos Haar [this message]
2009-05-19 1:05 ` RCU detected CPU 1 stall (t=4295904002/751 jiffies) Pid: 902, comm: md1_raid5 Neil Brown
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='12a901c9d805$119fef20$0400a8c0@dcccs' \
--to=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).