Date: Wed, 2 Feb 2005 14:31:53 +0100
From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>, Dave Jones <davej@codemonkey.org.uk>
Subject: Re: cpufreq problem wrt suspend/resume on Athlon64
Message-ID: <20050202133153.GD29579@elf.ucw.cz>
References: <200502021428.12134.rjw@sisk.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200502021428.12134.rjw@sisk.pl>
User-Agent: Mutt/1.5.6+20040907i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1151
Lines: 29

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.

Introduce _suspend() routine to cpufreq, and force cpu to 800MHz
during suspend(). Put it back to right frequency during resume().

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
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/