From: Thomas Renninger <trenn@suse.de>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: davej@codemonkey.org.uk, "Romain Liévin" <roms@lievin.net>,
cpufreq@lists.linux.org.uk
Subject: RE: Frequency can't switch on a dual Turion 64
Date: Sat, 13 Jan 2007 21:21:48 +0100 [thread overview]
Message-ID: <1168719708.14230.78.camel@sublime.site> (raw)
In-Reply-To: <1449F58C868D8D4E9C72945771150BDFD964C6@SAUSEXMB1.amd.com>
On Fri, 2007-01-12 at 09:06 -0600, Langsdorf, Mark wrote:
> > I may have detected a bug with the K8 cpu frequency driver
> > (powernow_k8.c). While the driver correctly
> > detect the 2 availables frequencies (800 & 1600 MHz), the
> > governor always uses the lowest one.
>
> It looks like the powernow-k8 driver correctly constructs
> a two entry frequency table and verifies it, and then
> reverifies a second frequency table with only 1 entry in
> it.
>
> I'm not familiar enough with the cpufreq code to guess
> why this is happening. I don't think it's a powernow-k8
> bug, but I suppose it could be doing something wrong.
I also think this is ACPI triggered...
does:
echo 1600000 > /sys/devices/../scaling_max_freq
helps, maybe shortly?
Is this an HP laptop?
Do you have some extended powernow/cpufreq configs in BIOS?
Is it getting too hot?
Check whether there exists a passive trip point in:
/proc/acpi/thermal_zone/*/trip_points
and whether
/proc/acpi/thermal_zone/*/temperature exceeds it.
Thomas
next prev parent reply other threads:[~2007-01-13 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 11:56 Frequency can't switch on a dual Turion 64 Romain Liévin
2007-01-12 15:06 ` Langsdorf, Mark
2007-01-13 20:21 ` Thomas Renninger [this message]
2007-01-13 21:55 ` Romain Liévin
2007-01-21 10:28 ` Romain Liévin
2007-01-21 11:46 ` Thomas Renninger
2007-01-21 15:45 ` Romain Liévin
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=1168719708.14230.78.camel@sublime.site \
--to=trenn@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=mark.langsdorf@amd.com \
--cc=roms@lievin.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.