From: lucke <lucke@o2.pl>
To: cpufreq@lists.linux.org.uk
Subject: Re: cpufreq and suspend
Date: Wed, 20 Sep 2006 23:09:13 +0200 [thread overview]
Message-ID: <200609202309.13897.lucke@o2.pl> (raw)
In-Reply-To: <1449F58C868D8D4E9C72945771150BDF15364F@SAUSEXMB1.amd.com>
On Wednesday 20 September 2006 20:53, you wrote:
> > >>http://lists.suspend2.net/lurker/message/20060827.234345.486
> >
> > 617dc.en.html
> >
> > >> Forgive me if this issue has been already mentioned, I can't
> > >> seem to find a way to search through archives.
> > >
> > >I'll go take a look at this.
> >
> > Is there any hope for a solution to this problem, Mark et al?
>
> It's been a busy week, and I just secured the system necessary to
> do the testing.
>
> Currently, I cannot reproduce with OpenSUSE 10.1 and the powersave
> tool. The system goes into S3 and comes out fine. Both cores are
> available and seem to be switching.
>
> I'll set up suspend2 this afternoon and try again.
Well, S3 doesn't work for me (doesn't want to wake up), thus I can't check how
cpufreq behaves with it. The problem occurs with suspend to disk (just
checked, not only with suspend2, but also with swsusp/powersave) - quite
logically it's where the problem could occur, as it has to go through BIOS
and kernel initialization phases again (I suppose suspend to RAM doesn't go
through that). I should've mentioned it earlier.
For completeness, MB is Asus A8N-E with latest BIOS.
I wish you a fruitful hunting,
Luke
next prev parent reply other threads:[~2006-09-20 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 18:44 cpufreq and suspend lucke
2006-09-20 18:53 ` Langsdorf, Mark
2006-09-20 21:09 ` lucke [this message]
2006-09-20 21:32 ` Langsdorf, Mark
-- strict thread matches above, loose matches on Subject: below --
2006-09-24 16:32 lucke
2006-09-15 20:25 lucke
2006-09-15 20:42 ` Langsdorf, Mark
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=200609202309.13897.lucke@o2.pl \
--to=lucke@o2.pl \
--cc=cpufreq@lists.linux.org.uk \
/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.