mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lukas Grässlin" <lukasgraesslin@gmx.de>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: changing the default cpufreq governor freezes laptop on suspend
Date: Sun, 19 Sep 2010 22:23:46 +0200	[thread overview]
Message-ID: <20100919202331.GA27077@home-server.graesslin.de> (raw)
In-Reply-To: <20100723011514.GD19985@gamma.logic.tuwien.ac.at>

Are there any news? I have exactly the same problem with stable 2.6.35.

It's not so a dramatic bug because the workaround (settings that
temporarily govenor in the pm-utils script to something that does not
exist, which means it is skipped) is ok and has actually no byeffects,
but it would still be nice to have that fixed :)

On Fri, Jul 23, 2010 at 10:15:14AM +0900, Norbert Preining wrote:
> Dear all,
> 
> (please Cc)
> 
> some time ago I switched from 2.6.35-rc1 to -rc2 and about the same time
> I regularly got problems with suspend to ram. I first thought that this
> is a graphics card issue 
> (see http://marc.info/?l=linux-kernel&m=127582534931581&w=2)
> but it turned out that using echo mem > /sys/power/state works very
> reliable.
> 
> I finally got around to check the scripts of pm-utils managing the
> suspend process here on Debian/sid, and I found that one of the
> scripts, before going to sleep, changes the default cpufreq governor
> to performance, doing in principle:
> 	cat /sys/devices/system/cpu/cpuN/cpufreq/scaling_governor > savedstate
> 	echo "performance" > /sys/.....
> Interestingly, as soon as I disabled these two line the suspend process
> became again as stable as before using pm-utils, and as stable as the
> echo mem method.
> 
> My laptop is intel core2:
> Intel(R) Core(TM)2 Duo CPU     P9500  @ 2.53GHz
> running Debian/sid, on self compiled git kernels pulled from Linus' repo.
> 
> Please let me know what further information I can provide, or how to help
> 
> Best wishes
> 
> Norbert
> ------------------------------------------------------------------------
> Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
> JAIST, Japan                                 TeX Live & Debian Developer
> DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
> ------------------------------------------------------------------------
> CLOVIS (q.v.)
> One who actually looks forward to putting up the Christmas decorations
> in the office.
> 			--- Douglas Adams, The Meaning of Liff
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 

-- 
Lukas Grässlin
GnuPG-Key: http://lg.ath.cx/lukasgraesslin@gmx.de.asc

  reply	other threads:[~2010-09-19 20:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23  1:15 Norbert Preining
2010-09-19 20:23 ` Lukas Grässlin [this message]
2010-09-21  2:06   ` Norbert Preining
2010-09-25 17:44     ` Lukas Grässlin
2010-09-27  1:01       ` Norbert Preining

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=20100919202331.GA27077@home-server.graesslin.de \
    --to=lukasgraesslin@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=preining@logic.at \
    /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

all inboxes | Powered by JetHome®