From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9151] Something broke cpufreq on laptop with lid behavior between 2.6.17 and 2.6.23
Date: Fri, 14 Dec 2007 20:51:55 -0800 (PST) [thread overview]
Message-ID: <20071215045155.72C7E11D109@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-9151-3570@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=9151
len.brown@intel.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |acpi-
| |bugzilla@lists.sourceforge.n
| |et
Summary|Something broke cpufreq on |Something broke cpufreq on
|laptop with lid behavior |laptop with lid behavior
| |between 2.6.17 and 2.6.23
------- Comment #7 from len.brown@intel.com 2007-12-14 20:51 -------
> When AC power is unplugged, the system clocks to its lowest speed but it also
> throttles to 25%. I don't want the throttling and have to un-throttle it by
> hand.
I've seen this bug before in the SuSE user-space.
Somebody got the idea that T-states save energy,
so they enable them when on battery.
I thought that they fixed it, but apparently they only disabled
this nonsense on MP systems, and UP systems remain broken.
There should be a check box someplace in the powersaved GUI
to disable this. The mystery is why you didn't see it also in 2.6.17.
Also, if the system is idle and running a sane governor
like ondemand, you should be in the lowest
P-state both before and after the transition from AC->DC.
> ... The governor switches to powersave. If the lid is closed
> on battery power, the CPU frequency begones the HIGHEST (2GHz).
> scaling_min_freq and scaling_max_freq report 600MHz but scaling_cur_freq
> reports 2GHz.
This again sounds like broken user-space policy software.
See if this still happens when in single-user mode
and none of that junk is running. But again, the mystery
is why you don't see the same issue with the same user-space
and the 2.6.17 kernel.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-12-15 4:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9151-3570@http.bugzilla.kernel.org/>
2007-10-12 18:00 ` [Bug 9151] Something broke cpufreq on laptop with lid behavior bugme-daemon
2007-10-12 18:00 ` bugme-daemon
2007-10-13 20:06 ` bugme-daemon
2007-11-22 23:41 ` bugme-daemon
2007-12-13 19:03 ` bugme-daemon
2007-12-13 23:10 ` bugme-daemon
2007-12-15 3:38 ` bugme-daemon
2007-12-15 4:51 ` bugme-daemon [this message]
2007-12-15 6:37 ` [Bug 9151] Something broke cpufreq on laptop with lid behavior between 2.6.17 and 2.6.23 bugme-daemon
2007-12-15 16:44 ` bugme-daemon
2007-12-18 5:11 ` bugme-daemon
2008-01-23 0:43 ` bugme-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=20071215045155.72C7E11D109@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=cpufreq@www.linux.org.uk \
/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