All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Paul E. McKenney" <paulmck@us.ibm.com>,
	RT <linux-rt-users@vger.kernel.org>
Subject: Re: 2.6.23-rc9-rt1
Date: Wed, 03 Oct 2007 08:46:54 -0500	[thread overview]
Message-ID: <47039D4E.7090206@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0710022134430.16284@gandalf.stny.rr.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Steven Rostedt wrote:
> 
> grmbl grmbl!!!
> 
> We are missing a match somewhere. Most likely in the suspend or resume
> code.  It's expected that if a CPU is idle with no ticks then the
> dynticks_progress_counter is even, otherwise it is odd. This check tells
> us that, in your case, this isn't the case. Which _is_ bad, and I wouldn't
> run it too long that way. It means that you can be getting false RCU grace
> period ends, which is not a good thing.
> 
> I could put a hack in that fixes the issue when detected, and still prints
> out a warning. I'll do that for now, until we find the problem area. I
> think the first warning probably had the want that corrupted us, and then
> we got flooded with warnings because we never fixed the situation.
> 
> Patch coming soon.
> 
> -- Steve
>> Ad infinitum. Not sure what you're looking for to be cleared in the enter and exit
>> functions, but it doesn't look like it's happening after a resume. Didn't seem to
>> affect the behavior of the kernel, since the network came up and I was able to
>> function normally (or as normally as I can function).
> 
> I'd reboot if I were you ;-)

Oh, I did :)

I've since suspended and resumed a couple of more times and have not seen your RCU
warnings, so it's not completely reproduceable.

Got any debugging code you want me to add, in case it pops up again?

Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHA51OHyuj/+TTEp0RAn6hAJwO3JHHk+2EVjpH7XcAYu+g5CC3DQCgj1lR
4Umv2vf2iDjxHNprCXfxhvI=
=SL/V
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-10-03 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 16:11 2.6.23-rc9-rt1 Steven Rostedt
2007-10-02 16:47 ` 2.6.23-rc9-rt1 Steven Rostedt
2007-10-03  1:02 ` 2.6.23-rc9-rt1 Clark Williams
2007-10-03  1:58   ` 2.6.23-rc9-rt1 Steven Rostedt
2007-10-03 13:46     ` Clark Williams [this message]
2007-10-03 17:28       ` 2.6.23-rc9-rt1 Steven Rostedt

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=47039D4E.7090206@redhat.com \
    --to=williams@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=paulmck@us.ibm.com \
    --cc=rostedt@goodmis.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.