From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Pavel Machek <pavel@suse.cz>,
kernel list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.27-rc6: nohz + s2ram = need to press keys to get progress
Date: Fri, 12 Sep 2008 22:45:44 +0200 [thread overview]
Message-ID: <200809122245.45723.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.1.10.0809122113270.13819@apollo.tec.linutronix.de>
On Friday, 12 of September 2008, Thomas Gleixner wrote:
> On Fri, 12 Sep 2008, Rafael J. Wysocki wrote:
>
> > On Friday, 12 of September 2008, Pavel Machek wrote:
> > > Hi!
> > >
> > > The old "you have to press keys to get machine to progress" seems to
> > > be back :-(. Thinkpad x60.
> >
> > I guess the last bunch of HPET/clockevents patches caused that to happen.
>
> Guessing is hardly a good method to get down to the root cause of
> those problems.
Well, sure.
> > We seem to be doing a "one step forward, one step back" thing here ...
>
> Well, the fixes for HPET/clockevents fix real bugs and there are no
> evident side effects vs. s2ram inside. quite the contrary.
So that must be something different.
Thanks,
Rafael
next prev parent reply other threads:[~2008-09-12 20:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 8:31 2.6.27-rc6: nohz + s2ram = need to press keys to get progress Pavel Machek
2008-09-12 19:13 ` Thomas Gleixner
2008-09-12 19:17 ` Rafael J. Wysocki
2008-09-12 19:15 ` Thomas Gleixner
2008-09-12 20:45 ` Rafael J. Wysocki [this message]
2008-09-12 21:05 ` Thomas Gleixner
2008-09-14 2:56 ` Thomas Gleixner
2008-09-14 10:09 ` Pavel Machek
2008-09-14 10:14 ` Pavel Machek
2008-09-14 17:35 ` Pavel Machek
2008-09-14 17:51 ` Thomas Gleixner
2008-09-14 18:12 ` Pavel Machek
2008-09-14 19:15 ` Thomas Gleixner
2008-09-15 9:19 ` Pavel Machek
2008-09-15 14:08 ` Thomas Gleixner
2008-09-15 19:26 ` Pavel Machek
2008-09-15 19:59 ` Pavel Machek
2008-09-16 14:16 ` Thomas Gleixner
2008-09-16 17:02 ` Thomas Gleixner
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=200809122245.45723.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox