From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9014] New: acpi-cpufreq uses too much power
Date: Thu, 13 Sep 2007 04:05:06 -0700 (PDT) [thread overview]
Message-ID: <bug-9014-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=9014
Summary: acpi-cpufreq uses too much power
Product: Power Management
Version: 2.5
KernelVersion: 2.6.22
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: rrs@researchut.com
Most recent kernel where this bug did not occur:
N/A
Distribution:
Debian
Hardware Environment:
Dell XPS M1210
Processor: Intel Core Duo 2.0 Ghz
RAM: 2 GB
GPU: nVIDIA
Software Environment:
Linux 2.6.22 with DynTicks and HI-RES Timers
Problem Description:
Since the time I changed from speedstep-centrino to acpi-cpufreq after reading
the deprecated warning, I get only 5 minutes of battery backup on my laptop.
This is ugly.
With speedstep-centrino, I get back to my 1-1.5hrs of battery backup.
Sep 13 15:07:11 learner kernel: speedstep-centrino with
X86_SPEEDSTEP_CENTRINO_ACPI config is deprecated.
Sep 13 15:07:11 learner kernel: Use X86_ACPI_CPUFREQ (acpi-cpufreq) instead.
Sep 13 15:07:11 learner powersaved: Starting powersaved with ACPI support
Steps to reproduce:
Use acpi-cpufreq instead on speedstep-centrino
--
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 reply other threads:[~2007-09-13 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 11:05 bugme-daemon [this message]
2007-09-13 19:56 ` [Bug 9014] acpi-cpufreq uses too much power 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=bug-9014-3570@http.bugzilla.kernel.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 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.