All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 58001] "ondemand" CPU governor never raises frequency (Dell XPS 12)
Date: Thu, 25 Sep 2014 14:31:56 +0000	[thread overview]
Message-ID: <bug-58001-12968-Adl3k6r9yB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-58001-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=58001

--- Comment #22 from Paul Johnson <pauljohn@ku.edu> ---
Is it possible that different Intel chips respond differently?  I'm running
Ubuntu 14.04 on 2 laptops and one has the problem, the other does not. 

On the Dell Precision m4600 laptop, I had the chronic problem that, after
suspend, I was always stuck at 800MHZ.  To fix that, I had to explicitly reset
the threshold lower.  Eventually, I found a script that did it


#!/bin/bash


## https://gist.github.com/Pyppe/6028707
# default with 13.04 is 95
SCALING_FILE=/sys/devices/system/cpu/cpufreq/ondemand/up_threshold

defvalue=70

if [ ! -f "$SCALING_FILE" ]; then
                echo "$SCALING_FILE not found"
                exit 1
fi

limit=${1:-$defvalue}

if [[ $limit -lt 100 && $limit -gt 30 ]]; then
                sudo bash -c "echo $limit > $SCALING_FILE"
else
                echo "Invalid value"
                exit 1
fi

However, on a Dell Latitude 6430u, I have no such problem.  Frequency scaling
works without qualification, before and after suspend.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2014-09-25 14:31 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 ` [Bug 58001] " bugzilla-daemon
2013-05-12 16:55 ` 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 [this message]
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=bug-58001-12968-Adl3k6r9yB@https.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 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.