From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugme-daemon@bugzilla.kernel.org
Subject: [Bug 9151] Something broke cpufreq on laptop with lid behavior
between 2.6.17 and 2.6.23
Date: Fri, 14 Dec 2007 22:37:57 -0800 (PST)
Message-ID: <20071215063757.904D811D109@picon.linux-foundation.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
In-Reply-To:
List-Id:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: cpufreq-bounces@lists.linux.org.uk
Errors-To: cpufreq-bounces+glkc-cpufreq=m.gmane.org+glkc-cpufreq=m.gmane.org@lists.linux.org.uk
To: cpufreq@www.linux.org.uk
http://bugzilla.kernel.org/show_bug.cgi?id=9151
------- Comment #8 from stevenm@umd.edu 2007-12-14 22:37 -------
My tests were done in single-user mode, console, no X, no laptop-mode, no dbus
or hal, nothing. As far as I could tell (and I stared at ps -e for a long time)
nothing could be running that was changing the CPU frequency, not even acpid.
The fact that the system was thinking it was at one frequency and actually
being at another (hence refusing to change) tells me it is a kernel problem.
Ie, I set it to 600. It is stuck at 2000. Setting it to 600 has no effect. But
setting it to 800 and then 600 worked fine. Go figure
--
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.