From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 58001] "ondemand" CPU governor never raises frequency (Dell XPS 12)
Date: Sun, 12 May 2013 15:32:26 +0000 (UTC) [thread overview]
Message-ID: <20130512153226.32AF911FB3B@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-58001-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=58001
--- Comment #1 from Viresh Kumar <viresh.kumar@linaro.org> 2013-05-12 15:32:26 ---
On Sat, May 11, 2013 at 3:02 PM, <bugzilla-daemon@bugzilla.kernel.org> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=58001
>
> Summary: "ondemand" CPU governor never raises frequency (Dell
> XPS 12)
> Product: Power Management
> Version: 2.5
> Kernel Version: 3.8.11-200.fc18.x86_64
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: cpufreq
> AssignedTo: cpufreq@vger.kernel.org
> ReportedBy: jylefort@gmail.com
> Regression: No
>
>
> On a Dell XPS 12 (Intel Core i7-3537U), I experience exactly the same symptoms
> as in bug #14771, except it has nothing to do with the power supply: I'm using
> the stock power supply, and the problematic behavior is observed both on
> battery and on AC power.
>
> If I keep the default settings, the CPU frequency never goes beyond the 800 MHz
> minimum, regardless of the CPU load.
>
> If I decrease /sys/devices/system/cpu/cpufreq/ondemand/up_threshold from the
> default value of 95 to 75, then the processors dynamically switch back and
> forth from 800 MHz to 2 GHz according to CPU load.
It sort of means system isn't loaded well :)
Can you paste/attach output of cpufreq-info?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2013-05-12 15:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 9:32 [Bug 58001] New: "ondemand" CPU governor never raises frequency (Dell XPS 12) bugzilla-daemon
2013-05-12 15:32 ` Viresh Kumar
2013-05-12 15:32 ` bugzilla-daemon [this message]
2013-05-12 16:55 ` [Bug 58001] " bugzilla-daemon
2013-05-13 3:48 ` Viresh Kumar
2013-05-13 3:48 ` bugzilla-daemon
2013-05-29 1:04 ` bugzilla-daemon
2013-06-07 14:49 ` bugzilla-daemon
2013-07-08 14:57 ` bugzilla-daemon
2013-07-08 15:01 ` bugzilla-daemon
2013-07-08 15:02 ` bugzilla-daemon
2013-07-09 1:28 ` bugzilla-daemon
2013-09-23 1:58 ` [Bug 58001] Raymond Auge
2013-09-23 8:30 ` [Bug 58001] "ondemand" CPU governor never raises frequency (Dell XPS 12) bugzilla-daemon
2013-10-14 11:08 ` bugzilla-daemon
2013-10-14 11:34 ` bugzilla-daemon
2013-10-14 12:23 ` bugzilla-daemon
2014-03-11 3:22 ` bugzilla-daemon
2014-03-11 3:26 ` bugzilla-daemon
2014-03-23 22:39 ` bugzilla-daemon
2014-03-23 22:45 ` bugzilla-daemon
2014-09-22 13:54 ` bugzilla-daemon
2014-09-24 22:18 ` bugzilla-daemon
2014-09-24 22:55 ` bugzilla-daemon
2014-09-24 22:56 ` bugzilla-daemon
2014-09-25 0:16 ` bugzilla-daemon
2014-09-25 0:59 ` bugzilla-daemon
2014-09-25 14:31 ` bugzilla-daemon
2014-10-23 8:03 ` bugzilla-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=20130512153226.32AF911FB3B@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).