From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 56071] Ondemand doesn't set correct low frequency
Date: Tue, 2 Apr 2013 10:08:08 +0000 (UTC) [thread overview]
Message-ID: <20130402100808.4D52811FB5B@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-56071-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=56071
--- Comment #7 from Thomas Renninger <trenn@suse.de> 2013-04-02 10:08:08 ---
> Is this also related to cpufreq ?
This is certainly ACPI related.
It's hard to guess, but your BIOS seem to request to limit cpufreq or
throttling.
Cpufreq limitation you should see in this line:
limiti hardware: 1.30 GHz - 2.10 GHz
from cpupower frequency-info output.
This should be 1.30 GHz - 1.30 GHz
or similar after you plugged in AC.
Best you increase ACPI debug output before plugging AC:
echo 0x20f >/sys/module/acpi/parameters/debug_level
echo 0xffffffff >/sys/module/acpi/parameters/debug_layer
then do the plugging, wait a second or two and reduce debugging again.
echo 0 >/sys/module/acpi/parameters/debug_level
echo 0 >/sys/module/acpi/parameters/debug_layer
This could produce quite some kernel output, so you may want to boot with
log_buf_len=16M
boot parameter.
Then attach dmesg and acpidump of your machine to the bug you created for the
AC issue (mixing up bugs is confusing if you add other people later).
Before you start with all this, make sure you have the latest BIOS installed.
ACPI bugs can be tricky, best follow instructions of Lan Tianyu.
Feel free to add me to CC.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2013-04-02 10:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 20:12 [Bug 56071] New: Ondemand doesn't set correct low frequency bugzilla-daemon
2013-04-01 20:13 ` [Bug 56071] " bugzilla-daemon
2013-04-01 20:37 ` bugzilla-daemon
2013-04-02 5:23 ` [Bug 56071] New: " Viresh Kumar
2013-04-02 5:23 ` [Bug 56071] " bugzilla-daemon
2013-04-02 6:16 ` bugzilla-daemon
2013-04-02 7:53 ` bugzilla-daemon
2013-04-02 8:57 ` bugzilla-daemon
2013-04-02 10:08 ` bugzilla-daemon [this message]
2014-09-22 13:44 ` 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=20130402100808.4D52811FB5B@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).