public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: ncunningham@linuxmail.org
Cc: Pavel Machek <pavel@ucw.cz>,
	Dominik Brodowski <linux@dominikbrodowski.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@codemonkey.org.uk>
Subject: Re: cpufreq problem wrt suspend/resume on Athlon64
Date: Fri, 4 Feb 2005 00:52:28 +0100	[thread overview]
Message-ID: <200502040052.28992.rjw@sisk.pl> (raw)
In-Reply-To: <1107473644.5727.6.camel@desktop.cunninghams>

On Friday, 4 of February 2005 00:34, Nigel Cunningham wrote:
> Hi.
> 
> On Fri, 2005-02-04 at 10:15, Rafael J. Wysocki wrote:
> > Instead of trying to blow up the battery I used the patch that forces the CPU
> > to 800 MHz and it apparently survives resuming on batteries - at least 3
> > times out of 3 attempts (I'll try some times more tomorrow).
> > 
> > It seems to boot at 1800 MHz, though, every time, according to
> > cpufreq_resume().
> 
> Sounds like some good work. Is 800 the minimum for your laptop?

Yes, it is.

> I'm just wondering how you know what speed to choose on other systems.

Well, I don't know.  It seems that for k8-based CPUs the minimum is
a reasonable choice, but it apparently is not so for other processors.

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"

  reply	other threads:[~2005-02-03 23:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 13:28 cpufreq problem wrt suspend/resume on Athlon64 Rafael J. Wysocki
2005-02-02 13:31 ` 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 [this message]
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=200502040052.28992.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.de \
    --cc=ncunningham@linuxmail.org \
    --cc=pavel@ucw.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