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: Mon, 6 Sep 2010 09:20:26 GMT	[thread overview]
Message-ID: <201009060920.o869KQar000565@demeter1.kernel.org> (raw)
In-Reply-To: <bug-17001-12968@https.bugzilla.kernel.org/>

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





--- Comment #11 from Thomas Renninger <trenn@suse.de>  2010-09-06 09:20:23 ---
Gerhard: You probably have another problem. Peter's problem seem to point to a
real kernel bug, you have to find out why the BIOS is limiting the frequency
(which the kernel is probably doing correct).
You find hints how to find that out here:
https://bugzilla.kernel.org/show_bug.cgi?id=16362
But best would be to open another bug as the reason why BIOS is limiting the
freq is probably another one. Update your BIOS first and double check whether
the problem persists. State HP Compaq 6910p again (in the title?) so that
others also find the issue quickly.

Peter: Could you try another kernel version. Either the latest 2.6.36-rcX or
easier and even better would be something like 2.6.27-32. I can help you to try
that out easily if you use openSUSE, otherwise you have to find out yourself,
but it shouldn't be that hard to additionally install and try out an older
kernel. Also check the "bias" ondemand governor setting (same dir(s) as
up_threshold), this must be zero. If it's not, it's probably that.
Unfortunately the ondemand governor is not very verbose about it's load
statistics, even with cpufreq.debug on.

-- 
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-09-06  9:20 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
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 [this message]
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=201009060920.o869KQar000565@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.