All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 17001] ondemand governor non-functional / ACPI P-states driver
Date: Thu, 26 Aug 2010 14:39:09 GMT	[thread overview]
Message-ID: <201008261439.o7QEd9dX023154@demeter1.kernel.org> (raw)
In-Reply-To: <bug-17001-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=17001





--- Comment #3 from Peter Ganzhorn <peter.ganzhorn@googlemail.com>  2010-08-26 14:38:45 ---
Sorry, using the performance governor was my bad - I almost always switch to
performace manually because working on that computer with 800MHz ist just
painful.

I rebooted the machine to get some clean results and ran some CPU intensive
calculations with matlab, the load was at 100% for quite some time and the
frequency did not change at all.
Temperature can't be the problem since the CPU temperature was reported as
35°C-40°C (I checked), with the performance governor the temperature will go
above 70°C before the CPU slows down because of too high temperature.

I'll append the information you requested now.
Please also note the following:

# cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
2001000 0
2000000 0
1600000 0
1200000 0
800000 84859

Was done with ondemand governor enabled this time ;)

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2010-08-26 14:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 11:52 [Bug 17001] New: ondemand governor non-functional / ACPI P-states driver bugzilla-daemon
2010-08-25 20:57 ` [Bug 17001] " bugzilla-daemon
2010-08-26 11:14 ` bugzilla-daemon
2010-08-26 14:39 ` bugzilla-daemon [this message]
2010-08-26 14:40 ` bugzilla-daemon
2010-08-26 15:14 ` bugzilla-daemon
2010-08-27 12:21 ` bugzilla-daemon
2010-08-27 12:24 ` bugzilla-daemon
2010-08-27 12:27 ` bugzilla-daemon
2010-09-06  1:47 ` bugzilla-daemon
2010-09-06  2:30 ` bugzilla-daemon
2010-09-06  9:20 ` bugzilla-daemon
2010-09-06  9:37 ` bugzilla-daemon
2010-09-06 10:13 ` bugzilla-daemon
2010-09-06 10:22 ` bugzilla-daemon
2010-09-06 10:29 ` bugzilla-daemon
2010-09-06 10:46 ` bugzilla-daemon
2010-10-15 10:11 ` bugzilla-daemon

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=201008261439.o7QEd9dX023154@demeter1.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@vger.kernel.org \
    /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.