From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Dave Jones <davej@codemonkey.org.uk>, Pavel Machek <pavel@suse.cz>
Subject: cpufreq problem wrt suspend/resume on Athlon64
Date: Wed, 2 Feb 2005 14:28:11 +0100 [thread overview]
Message-ID: <200502021428.12134.rjw@sisk.pl> (raw)
Hi,
I have noticed that the condition (cur_freq != cpu_policy->cur), which is
unlikely() according to cpufreq.c:cpufreq_resume(), occurs on every resume
on my box (Athlon64-based Asus). Every time the box resumes, I get a message
like that:
Warning: CPU frequency out of sync: cpufreq and timing core thinks of 1600000, is 1800000 kHz.
(the numbers vary: there may be 800000 vs 1600000 or even 800000 vs 1800000).
Also, when the box is suspended on AC power and resumed on batteries, it often
reboots.
Please let me know if there's anything (relatively simple :-)) that I can do
about it.
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
next reply other threads:[~2005-02-02 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 13:28 Rafael J. Wysocki [this message]
2005-02-02 13:31 ` cpufreq problem wrt suspend/resume on Athlon64 Pavel Machek
2005-02-03 0:08 ` Rafael J. Wysocki
2005-02-03 10:41 ` Pavel Machek
2005-02-03 10:56 ` Dominik Brodowski
2005-02-03 10:58 ` Pavel Machek
2005-02-03 11:01 ` Dominik Brodowski
2005-02-03 11:30 ` Rafael J. Wysocki
2005-02-03 12:40 ` Dominik Brodowski
2005-02-03 13:20 ` Rafael J. Wysocki
2005-02-03 14:22 ` Pavel Machek
2005-02-03 23:15 ` Rafael J. Wysocki
2005-02-03 23:34 ` Nigel Cunningham
2005-02-03 23:52 ` Rafael J. Wysocki
2005-02-07 12:38 ` cpufreq problem wrt suspend/resume on Athlon64 [update] Rafael J. Wysocki
2005-02-03 14:20 ` cpufreq problem wrt suspend/resume on Athlon64 Pavel Machek
2005-02-03 21:46 ` Rafael J. Wysocki
2005-02-03 22:00 ` Pavel Machek
2005-02-03 23:37 ` Rafael J. Wysocki
2005-02-03 22:01 ` Pavel Machek
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=200502021428.12134.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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