All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	Linux-pm mailing list <linux-pm@lists.osdl.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.27-rc6: nohz + s2ram = need to press keys to get progress
Date: Sun, 14 Sep 2008 19:35:36 +0200	[thread overview]
Message-ID: <20080914173536.GA1687@elf.ucw.cz> (raw)
In-Reply-To: <20080914101406.GA1625@elf.ucw.cz>

On Sun 2008-09-14 12:14:06, Pavel Machek wrote:
> On Sun 2008-09-14 12:09:13, Pavel Machek wrote:
> > On Sun 2008-09-14 04:56:48, Thomas Gleixner wrote:
> > > Pavel,
> > > 
> > > On Fri, 12 Sep 2008, Pavel Machek wrote:
> > > > The old "you have to press keys to get machine to progress" seems to
> > > > be back :-(. Thinkpad x60.
> > > 
> > > Is there a chance that we get some more information than that ?
> > 
> > Yep.
> > 
> > It does not happen after _every_ s2ram, but when it happens the system
> > limps around in half-dead state with non-blinking cursor etc. Next
> > s2ram will not fix it.
> > 
> > nohz=off helps.
> > 
> > Will try 2.6.27-rc6 w/o any custom patches next (not that I have
> > anything interesting in that area), and then probably 2.6.26.
> 
> It _does_ happen with mainline 2.6.27-rc6.

s2ram hs problem in mainline 2.6.26, too. (Different problem: no
ammount pressing shift helps there.) nohz=off cures it, too.

How to proceed?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-09-14 17:35 UTC|newest]

Thread overview: 21+ 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
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 [this message]
2008-09-14 17:51         ` Thomas Gleixner
2008-09-14 18:12           ` Pavel Machek
2008-09-14 19:15             ` Thomas Gleixner
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
  -- strict thread matches above, loose matches on Subject: below --
2008-09-14 15:49 Andreas Mohr

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=20080914173536.GA1687@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=rjw@sisk.pl \
    --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.