public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: 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:37:45 +0100	[thread overview]
Message-ID: <200502040037.46251.rjw@sisk.pl> (raw)
In-Reply-To: <20050203220051.GA1098@elf.ucw.cz>

Hi,

On Thursday, 3 of February 2005 23:00, Pavel Machek wrote:
> Hi!
> 
> > > You may not run k8 notebook on max frequency on battery. Your system
> > > will crash; and you might even damage battery.
> > 
> > When I don't compile in cpufreq, it seems to run at 1,8 GHz (the max)
> > all the time, on AC power as well as on battery.  Along with what you're
> > saying it leads to the conclusion that in fact I have to compile in cpufreq
> > or I can damage the battery otherwise.  Is that right?
> 
> Yes.
> 
> [It is strange, k8 notebooks are supposed to boot at 800MHz. Older
> arima prototype got it wrong and in 50% crashed during boot on battery
> power. OTOH if your machine is stable at battery at 1.8GHz... well
> then we'll have to search for other problem in cpufreq&resume....]

It seems to be stable, although I must admit I haven't run it on battery power
for longer than 5 min. without cpufreq and now I'm a bit reluctant to try. ;-)

Anyway the failing case seems to be when the frequency during suspend
is higher than during resume (eg when the image is created at 1800 MHz and the
CPU is running at 800 MHz right after restoring the image).
 
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:37 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
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 [this message]
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=200502040037.46251.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.de \
    --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