From: Andy Isaacson <adi@hexapodia.org>
To: "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: rcu_sched_state detected stall on CPU 0, 3.0-rc2
Date: Sun, 12 Jun 2011 12:58:56 -0700 [thread overview]
Message-ID: <20110612195856.GA11580@hexapodia.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
My Thinkpad x201s threw some errors (?) a few minutes after resuming
from suspend-to-ram this morning.
[56415.672140] INFO: rcu_sched_state detected stall on CPU 0 (t=15000 jiffies)
Nothing jumps out of the backtraces at me. Full dmesg and config
attached. This was my first StR since upgrading from 2.6.39, let's see
if it fails again when I suspend after sending this email. :)
-andy
[-- Attachment #2: trace.gz --]
[-- Type: application/octet-stream, Size: 27327 bytes --]
[-- Attachment #3: config-trim.gz --]
[-- Type: application/octet-stream, Size: 8350 bytes --]
next reply other threads:[~2011-06-12 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 19:58 Andy Isaacson [this message]
2011-06-12 23:11 ` rcu_sched_state detected stall on CPU 0, 3.0-rc2 Andy Isaacson
2011-06-12 23:55 ` Andy Isaacson
2011-06-13 2:30 ` Ben Hutchings
2011-06-13 6:04 ` Andy Isaacson
2011-06-19 21:20 ` Andy Isaacson
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=20110612195856.GA11580@hexapodia.org \
--to=adi@hexapodia.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.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