From: Philipp Herz - Profihost AG <p.herz@profihost.ag>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: stalled CPUs after upgrading to 3.0.28
Date: Fri, 08 Jun 2012 12:14:40 +0200 [thread overview]
Message-ID: <4FD1D090.2060904@profihost.ag> (raw)
Hi,
after upgrading linux kernel to version 3.0.28 some systems randomly
freeze, because of "rcu_sched_state" stalling CPU(s).
Is there anything known to this problem? How can it be fixed?
Thanks and regards,
Philipp
+------------------------------------------------------------------+
INFO: rcu_sched_state detected stall on CPU 3 (t=6361556 jiffies)
sending NMI to all CPUs:
NMI backtrace for cpu 2
CPU 2
Modules linked in: xt_tcpudp coretemp k8temp ipt_REJECT
iptable_filter ip_tables x_tables ipv6 i2c_i801 i2c_core [last unloaded:
scsi_wait_scan]
Pid: 24170, comm: httpd Not tainted 2.6.40.28p4 #1 FUJITSU SIEMENS
D2581-A5 /D2581-A5
RIP: 0010:[<ffffffff815c45a9>] [<ffffffff815c45a9>]
_raw_spin_lock+0x19/0x20
RSP: 0018:ffff8801153e5dd8 EFLAGS: 00000293
RAX: 000000000000056d RBX: ffff88010d2846d0 RCX: 0000000000000000
RDX: 000000000000056a RSI: 0000000000000003 RDI: ffff88010d2846d0
RBP: ffff8801153e5dd8 R08: ffff8801153e5e58 R09: dead000000100100
R10: 0000000000000000 R11: ffffea0003e2eb28 R12: ffff8801153e5e58
R13: ffff8801153e5e70 R14: ffff880012855348 R15: ffff8801153e5e58
FS: 00007f1ea2c2a740(0000) GS:ffff88013fd00000(0000)
knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1ea00ee7e5 CR3: 0000000133ed7000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process httpd (pid: 24170, threadinfo ffff8801153e4000, task
ffff880132180000)Stack:
ffff8801153e5df8 ffffffff8129a0f4 ffff8801153e5e18 0000000000c30003
ffff8801153e5e18 ffffffff8129a120 ffff8801153e5e18 ffff88013b2e4060
ffff8801153e5ea8 ffffffff8129c942 ffff8801395b1a40 ffff880100c30003
reply other threads:[~2012-06-08 10:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FD1D090.2060904@profihost.ag \
--to=p.herz@profihost.ag \
--cc=linux-kernel@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 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.