From: Clark Williams <williams@redhat.com>
To: paulmck@linux.vnet.ibm.com
Cc: Thomas Gleixner <tglx@linutronix.de>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: [RT] RCU splat on 2.6.33.4-rt20
Date: Thu, 20 May 2010 08:59:27 -0500 [thread overview]
Message-ID: <20100520085927.480047d4@torg> (raw)
In-Reply-To: <20100520032246.GB2708@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
On Wed, 19 May 2010 20:22:46 -0700
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> On Wed, May 19, 2010 at 09:19:11PM -0500, Clark Williams wrote:
> > Thomas/Paul,
> >
> > Resumed my laptop (T60, 64-bit kernel) and after about five
> > minutes of doing nothing but surfing with firefox, got the following
> > RCU stall notification from a 2.6.33.4-rt20 kernel:
> >
> > INFO: RCU detected CPU 1 stall (t=0 jiffies)
>
> Hmmm... "t=0 jiffies". I wonder if the hibernation/resumption confused
> the stall-warning code. My first thought was that an RCU grace period
> had spanned the hibernation, but that would not be consistent with it
> waiting five minutes after resumption to splat.
>
> I will look into this.
>
Don't take that "five minutes" as anything approaching some degree of
accuracy. It could have been quicker; I was distracted and not even
touching the keyboard when a loud beep sounded and I had to poke around
a bit to realize that an NMI backtrace had triggered.
Depending on your timeout values, I think that it's quite reasonable to
suspect that an RCU spanned the suspend/resume.
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-05-20 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 2:19 [RT] RCU splat on 2.6.33.4-rt20 Clark Williams
2010-05-20 3:22 ` Paul E. McKenney
2010-05-20 13:59 ` Clark Williams [this message]
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=20100520085927.480047d4@torg \
--to=williams@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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.