From: pthomas8589@gmail.com (Paul Thomas)
To: linux-arm-kernel@lists.infradead.org
Subject: at91san9g20, INFO: RCU detected CPU 0 stall
Date: Thu, 28 Jan 2010 21:40:15 -0700 [thread overview]
Message-ID: <c785bba31001282040o65a9dd30mebeeb72631936c95@mail.gmail.com> (raw)
Hello,
I'm getting the following errors on the console:
INFO: RCU detected CPU 0 stall (t=1000 jiffies)
INFO: RCU detected CPU 0 stall (t=4000 jiffies)
INFO: RCU detected CPU 0 stall (t=7000 jiffies)
...
The system is mostly unresponsive at this point. The console & ssh are
unresponsive, but ping still works (Is that just the PHY responding?).
I'm pretty sure this is because I enabled NO_HZ, HIGH_RES_TIMERS,
CONFIG_PREEMPT & ATMEL_TCLIB in the kernel. I've attached the .config file.
I'm using 2.6.33-rc2 without the maxim.org.za patch, and one minor
socket-can patch. I'm been using various versions of this same kernel for
weeks without any problems, and just today I wanted to use the high res
timers so I enabled that stuff in the kernel. I'm using the at91sam9g20
processor. I don't think it matters, but the command that triggered this was
"svn --version". After a reboot the "svn --version" command is fine.
What does this error/info mean? How is it different from a kernel panic?
Have other people seen this on the at91 devices?
thanks,
Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100128/e7f2f2ed/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/octet-stream
Size: 33497 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100128/e7f2f2ed/attachment-0001.obj>
reply other threads:[~2010-01-29 4:40 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=c785bba31001282040o65a9dd30mebeeb72631936c95@mail.gmail.com \
--to=pthomas8589@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).