From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 12389] acpi-cpufreq doesn't detect speed limit when cold booted on battery
Date: Sat, 6 Nov 2010 20:04:56 GMT [thread overview]
Message-ID: <201011062004.oA6K4uSr024113@demeter2.kernel.org> (raw)
In-Reply-To: <bug-12389-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=12389
Thomas Renninger <trenn@suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |trenn@suse.de
Component|cpufreq |Config-Processors
AssignedTo|cpufreq@vger.kernel.org |acpi_config-processors@kern
| |el-bugs.osdl.org
Product|Power Management |ACPI
--- Comment #3 from Thomas Renninger <trenn@suse.de> 2010-11-06 20:04:54 ---
This should be an ACPI, not a cpufreq bug.
Some things you could check:
- BIOS up-to-date?
- Is the limitation done through _PPC:
cat /sys/devices/system/cpu/cpu0/cpufreq/bios_limit
The bios limit (_PPC) was not evaluated at (processor.ko) driver load time, but
only when CPU notification events where thrown. It sounds like you see this.
This got fixed by commit:
455c0d71d46e86b0b7ff2c9dcfc19bc162302ee9
Above patch could make trouble on other systems and you set "Fedora tree".
Can you double check that above commit is included in your tested kernel.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
prev parent reply other threads:[~2010-11-06 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12389-12968@https.bugzilla.kernel.org/>
2010-11-05 18:11 ` [Bug 12389] acpi-cpufreq doesn't detect speed limit when cold booted on battery bugzilla-daemon
2010-11-05 18:12 ` bugzilla-daemon
2010-11-06 20:04 ` bugzilla-daemon [this message]
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=201011062004.oA6K4uSr024113@demeter2.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.