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: Tue, 22 Jan 2008 16:43:38 -0800 (PST) [thread overview]
Message-ID: <20080123004338.4F34410806A@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-9151-3570@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=9151
trenn@suse.de changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|cpufreq@www.linux.org.uk |trenn@suse.de
Status|NEW |ASSIGNED
------- Comment #11 from trenn@suse.de 2008-01-22 16:43 -------
On a Dell, I expect this is because the BIOS itself sets the frequncy when
(un-)plugging AC behind the kernel's back, instead of sending a ACPI notify
0x80 on the CPU and let the OS reevaluate _PPC and then let the kernel adjust
frequency (it should do this also, but it also sets the freq itself AFAIK).
I try to get a DELL and track this down.
I take over this bug and hope I can set it to a duplicate to bug #9708, these
are the same...
--
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.
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2008-01-23 0:43 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 ` [Bug 9151] Something broke cpufreq on laptop with lid behavior between 2.6.17 and 2.6.23 bugme-daemon
2007-12-15 6:37 ` bugme-daemon
2007-12-15 16:44 ` bugme-daemon
2007-12-18 5:11 ` bugme-daemon
2008-01-23 0:43 ` bugme-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=20080123004338.4F34410806A@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