All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: muskatnuss@gmx.at
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Amd Turion TL-52 X2 on Amilo PA 1510> No way to change Frequency!
Date: Wed, 30 May 2007 19:05:30 +0200	[thread overview]
Message-ID: <1180544730.27891.47.camel@queen.suse.de> (raw)
In-Reply-To: <1180543374.5534.6.camel@Tux-Devil>

On Wed, 2007-05-30 at 18:42 +0200, Muskat Nuss wrote:
> So i tried this commands after adding cat /dev/zero >/dev/null 
> to my boot file.
> 
> cat /proc/acpi/thermal_zone/*/state
> state:                   ok
> 
> cat /proc/acpi/thermal_zone/*/{trip_points,temperature}
> critical (S5):           100 C
> temperature:             51 C
> 
> so i already done an bios update to newest version 7.0c
> and checked my bios but no "_PPC BIOS freq limitation"
> anywhere
> 
> now i tried using only the ondemand governor.
> so i got as default Performance, so i also tried 
> ondemand .... Nothing happens to my cpu.

Hmm, it can't be the passive trip point, your BIOS doesn't declare one.
Only thing I could imagine is _PPC or some weird cpufreq bug.

Could you open a bug entry on bugzilla.kernel.org, put me into CC and
attach acpidump and dmesg output.

If you know how to compile the latest kernel, it would be great if you
could add CPU_FREQ_DEBUG=y and ACPI_DEBUG=y in the compile options and
boot with cpufreq.debug=7 and again post dmesg output after powernow-k8
got loaded and ondemand got activated for a short while.


   Thomas

  reply	other threads:[~2007-05-30 17:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28 19:12 Amd Turion TL-52 X2 on Amilo PA 1510> No way to change Frequency! Muskat Nuss
2007-05-29 17:51 ` Langsdorf, Mark
2007-05-29 19:15   ` Muskat Nuss
2007-05-29 19:42     ` Langsdorf, Mark
2007-05-30  7:15       ` Thomas Renninger
2007-05-30 16:42         ` Muskat Nuss
2007-05-30 17:05           ` Thomas Renninger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-29 22:48 Muskat Nuss
2007-05-25 20:41 Muskat Nuss
2007-05-25 20:22 Muskat Nuss
2007-05-25  5:09 Patrick Oberdorfer
2007-05-25 15:19 ` Langsdorf, Mark
2007-05-24 22:14 Muskat Nuss

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=1180544730.27891.47.camel@queen.suse.de \
    --to=trenn@suse.de \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=muskatnuss@gmx.at \
    /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.