From: Matthias Luescher <m.luescher@vtxmail.ch>
To: <tglx@linutronix.de>, <rostedt@goodmis.org>
Cc: <linux-rt-users@vger.kernel.org>
Subject: Shutdown/poweroff fails with 2.6.24.7-rt27 and 2.6.26.8-rt16
Date: Mon, 23 Feb 2009 09:27:18 +0100 [thread overview]
Message-ID: <29325.1235377638@vtxmail.ch> (raw)
Dear rt experts
With the latest 2.6.24 and 2.6.26 rt patches my PCs (Core Duo and Core 2 Duo) do not power off
anymore when I shut them down. The last messages that appear are:
Disabling non-boot CPUs
CPU0 attaching NULL sched-domain
CPU1 attaching NULL sched-domain
In the kernel bugzilla I found the following helpful entry:
http://bugzilla.kernel.org/show_bug.cgi?id=11725
(clockevents: broadcast fixup possible waiters)
So I did some tests:
2.6.24
------
With rt20 the following two patches got added:
7300711e8c6824fcfbd42a126980ff50439d8dd0.patch
7300711e8c6824fcfbd42a126980ff50439d8dd0-fix.patch
I removed both of them and my PCs are powering off again.
2.6.26
------
With the stable kernel version 2.6.26.6 the following commit was added:
clockevents: broadcast fixup possible waiters: 92741d2d653769b582015c6a379e7b46e113435d
When I revert this commit my PCs are powering off again.
2.6.29
------
2.6.29-rc4-rt2 is ok!
So my question is:
Is it ok to remove the change "clockevents: broadcast fixup possible waiters" from the
2.6.24 and 2.6.26 kernel version?
(From the commit comment "Until the C1E patches arrived..." I guess that it could be ok since
the C1E patches were -as far as I can guess - added to the kernel after 2.6.26.)
Best regards
Matthias
reply other threads:[~2009-02-23 8:27 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=29325.1235377638@vtxmail.ch \
--to=m.luescher@vtxmail.ch \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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.