From: Daniel Gryniewicz <dang@fprintf.net>
To: Dave Jones <davej@redhat.com>
Cc: Robert Love <rml@ximian.com>,
Matthew Garrett <mgarrett@chiark.greenend.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Laptops & CPU frequency
Date: Wed, 14 Jan 2004 14:11:48 -0500 [thread overview]
Message-ID: <1074107508.4549.10.camel@localhost> (raw)
In-Reply-To: <20040114045945.GB23845@redhat.com>
On Tue, 2004-01-13 at 23:59, Dave Jones wrote:
> Of all the implementations I've played with (longhaul/powernow/speedstep-smi)
> speedstep is the only one that does funky shit with SMM. The others are quite
> dumb (and friendly) in comparison. (Ie, nothing happens on power source change)
I have an athlon-xp laptop (HP pavilion ze4500) with powernow that
definitely goes into low power mode when the plug is pulled. The screen
goes dark, and everything slows down. And, it appears to be some kind
of percentage of current speed, because if I'm in powersave mode (532000
Hz rather than 1795500), then it gets unbearably slow. However,
bogomips is not updated when I pull the plug. I've never run for any
length of time with boot-on-power-then-pull-the-plug, because I only do
that to go from one plug to another. If I'm running without the plug, I
generally booted that way. I use the k7-powernow module for my
powersaving.
[14:07:15 athena] dang> cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : mobile AMD Athlon(tm) XP2200+
stepping : 1
cpu MHz : 1788.828
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca
cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow
bogomips : 1777.66
--
Daniel Gryniewicz <dang@fprintf.net>
next prev parent reply other threads:[~2004-01-14 19:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 2:56 Laptops & CPU frequency jlnance
2004-01-11 3:17 ` Robert Love
2004-01-11 4:12 ` Valdis.Kletnieks
2004-01-11 6:16 ` Willy Tarreau
2004-01-11 10:27 ` Xavier Bestel
2004-01-11 10:33 ` Xavier Bestel
2004-01-12 16:58 ` Jerry Cooperstein
2004-01-12 21:19 ` Xavier Bestel
2004-01-12 19:52 ` john stultz
2004-01-12 20:11 ` Disconnect
2004-01-12 23:19 ` john stultz
2004-01-12 21:28 ` Xavier Bestel
2004-01-12 22:07 ` john stultz
2004-01-13 9:13 ` Xavier Bestel
2004-01-11 17:06 ` Matthew Garrett
2004-01-11 17:13 ` Robert Love
2004-01-11 17:44 ` Matthew Garrett
2004-01-11 17:54 ` Robert Love
2004-01-14 4:59 ` Dave Jones
2004-01-14 19:11 ` Daniel Gryniewicz [this message]
2004-01-14 19:17 ` Robert Love
2004-01-14 19:23 ` Daniel Gryniewicz
2004-01-15 20:42 ` Pavel Machek
2004-01-15 21:18 ` Daniel Gryniewicz
2004-01-15 22:21 ` John Bradford
2004-01-15 22:48 ` Pavel Machek
2004-01-19 17:44 ` Ducrot Bruno
2004-01-16 10:47 ` 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=1074107508.4549.10.camel@localhost \
--to=dang@fprintf.net \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarrett@chiark.greenend.org.uk \
--cc=rml@ximian.com \
/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