From: Clark Williams <williams@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>,
"Paul E. McKenney" <paulmck@us.ibm.com>
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Re: 2.6.23-rc9-rt1
Date: Tue, 02 Oct 2007 20:02:41 -0500 [thread overview]
Message-ID: <4702EA31.4020102@redhat.com> (raw)
In-Reply-To: <1191341473.5642.36.camel@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steven Rostedt wrote:
> That last change (new Preempt RCU) is highly experimental!!!
> We are currently testing it now, although it has been through some
> minor tests already, we haven't declared it stable yet.
>
> This new implementation might shave your cat, eat your dog and
> make your children miss the bus and be late for school.
> You have been warned! As is said many times on this list
> "If it breaks, you get to keep the pieces". So don't come crying
> to us if something terrible happens, but please let us know
> so that we can try to fix what broke.
>
> That said, please test it as much as possible. We are happy with
> the new implementation, but it's still young, and we want to
> shake out the problems so it can be pushed up into mainline.
>
Luckily, I'm currently catless, dogless and childless, so no harm done :)
I'm running this kernel on a Thinkpad T60 (Core2 Duo, x86_64). When I suspended to
RAM and then resumed, my syslog window started scrolling the following:
Oct 2 19:45:46 localhost kernel: [<ffffffff8020ac90>] mwait_idle+0x0/0x5f
Oct 2 19:45:46 localhost kernel: [<ffffffff8020ac05>] cpu_idle+0xc7/0xee
Oct 2 19:45:46 localhost kernel: [<ffffffff8021c6f3>] start_secondary+0x2e4/0x2f5
Oct 2 19:45:46 localhost kernel:
Oct 2 19:45:46 localhost kernel: WARNING: at include/linux/rcupreempt.h:91
rcu_enter_nohz()
Oct 2 19:45:46 localhost kernel:
Oct 2 19:45:46 localhost kernel: Call Trace:
Oct 2 19:45:46 localhost kernel: [<ffffffff80254a0b>]
tick_nohz_stop_sched_tick+0x1c6/0x2aa
Oct 2 19:45:46 localhost kernel: [<ffffffff8020ac90>] mwait_idle+0x0/0x5f
Oct 2 19:45:46 localhost gpm[2095]: *** err [gpm.c(529)]:
Oct 2 19:45:46 localhost gpm[2095]: select(): Interrupted system call
Oct 2 19:45:46 localhost kernel: [<ffffffff8020ab80>] cpu_idle+0x42/0xee
Oct 2 19:45:46 localhost kernel: [<ffffffff8021c6f3>] start_secondary+0x2e4/0x2f5
Oct 2 19:45:46 localhost kernel:
Oct 2 19:45:46 localhost kernel: WARNING: at include/linux/rcupreempt.h:99
rcu_exit_nohz()
Oct 2 19:45:46 localhost kernel:
Oct 2 19:45:46 localhost kernel: Call Trace:
Oct 2 19:45:46 localhost kernel: [<ffffffff80254b71>]
tick_nohz_restart_sched_tick+0x82/0x17d
Oct 2 19:45:46 localhost kernel: [<ffffffff8020ac90>] mwait_idle+0x0/0x5f
Oct 2 19:45:46 localhost kernel: [<ffffffff8020ac05>] cpu_idle+0xc7/0xee
Oct 2 19:45:46 localhost kernel: [<ffffffff8021c6f3>] start_secondary+0x2e4/0x2f5
Oct 2 19:45:46 localhost kernel:
Oct 2 19:45:46 localhost kernel: WARNING: at include/linux/rcupreempt.h:91
rcu_enter_nohz()
Oct 2 19:45:46 localhost kernel:
Oct 2 19:45:46 localhost kernel: Call Trace:
Oct 2 19:45:46 localhost kernel: [<ffffffff80254a0b>]
tick_nohz_stop_sched_tick+0x1c6/0x2aa
Oct 2 19:45:46 localhost kernel: [<ffffffff8020ac90>] mwait_idle+0x0/0x5f
Oct 2 19:45:46 localhost kernel: [<ffffffff8020ab80>] cpu_idle+0x42/0xee
Oct 2 19:45:46 localhost kernel: [<ffffffff8021c6f3>] start_secondary+0x2e4/0x2f5
Oct 2 19:45:46 localhost kernel:
Oct 2 19:45:46 localhost kernel: WARNING: at include/linux/rcupreempt.h:99
rcu_exit_nohz()
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).
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHAuoxHyuj/+TTEp0RAtwQAJ41+q49fJXmKB9+WKdphDFc/iUcyACeOgGF
5JV0gQb+fFuCf2MDjMuTyVA=
=pSNr
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-10-03 1:03 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 ` Clark Williams [this message]
2007-10-03 1:58 ` 2.6.23-rc9-rt1 Steven Rostedt
2007-10-03 13:46 ` 2.6.23-rc9-rt1 Clark Williams
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=4702EA31.4020102@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.