public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Christian Hesse <mail@earthworm.de>
Cc: linux-kernel@vger.kernel.org, Jan De Luyck <lkml@kcore.org>,
	Tony Lindgren <tony@atomide.com>
Subject: Re: [2.6.12.3] dyntick 050610-1 breaks makes S3 suspend
Date: Sun, 24 Jul 2005 16:23:18 +0200	[thread overview]
Message-ID: <20050724142318.GA1778@elf.ucw.cz> (raw)
In-Reply-To: <200507231451.04630.mail@earthworm.de>

Hi!

> > I recently tried out dyntick 050610-1 against 2.6.12.3, works great, it
> > actually makes a noticeable difference on my laptop's battery life. I don't
> > have hard numbers, lets just say that instead of the usual ~3 hours i get
> > out of it, i was ~4 before it started nagging, usual use pattern at work.
> >
> > The only gripe I have with it that it stops S3 from working. If the patch
> > is compiled in the kernel, it makes S3 suspend correctly, but resuming goes
> > into a solid hang (nothing get's it back alive, have to keep the
> > powerbutton for ~5 secs to shutdown the system)
> >
> > Anything I could test? The logs don't give anything useful..
> 
> I reported this some time ago [1], but there's no sulution so far...
> 
> [1] http://groups.google.com/groups?selm=4b4NI-7mJ-9%40gated-at.bofh.it

Does it also break if swsusp? Does it break if you replace enter sleep
function with some kind of dummy functions? (Or perhaps S1 is enough
for this test?)
								Pavel
-- 
teflon -- maybe it is a trademark, but it should not be.

  reply	other threads:[~2005-07-24 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-23 12:35 [2.6.12.3] dyntick 050610-1 breaks makes S3 suspend Jan De Luyck
2005-07-23 12:50 ` Christian Hesse
2005-07-24 14:23   ` Pavel Machek [this message]
2005-07-24 15:11     ` Jan De Luyck
2005-07-25 10:27   ` Tony Lindgren
2005-07-25 10:46     ` Christian Hesse

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=20050724142318.GA1778@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@kcore.org \
    --cc=mail@earthworm.de \
    --cc=tony@atomide.com \
    /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