All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9708] New: powersave governor does not work when power cable gets plugged in
Date: Mon,  7 Jan 2008 13:11:39 -0800 (PST)	[thread overview]
Message-ID: <bug-9708-3570@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=9708

           Summary: powersave governor does not work when power cable gets
                    plugged in
           Product: Power Management
           Version: 2.5
     KernelVersion: 2.6.24-rc6-default
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@www.linux.org.uk
        ReportedBy: deller@gmx.de


Hardware Environment:
HP NC6000 Laptop (Intel(R) Pentium(R) M processor 1.60GHz)

Problem Description:
cpufreq powermanagemnt does work pretty ok.
Nevertheless, I face a problem when I suddenly plug in the power cable.

Machine has no load, nevertheless I then can see (even minutes after I plugged
in the power cable):

[root@halden cpufreq]# uptime &&  grep ""
/sys/devices/system/cpu/cpu0/cpufreq/*

 21:57:23 up  1:04,  3 users,  load average: 0.09, 0.08, 0.09

/sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:1600000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1600000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:1600000
1400000 1200000 1000000 800000 600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:conservative
ondemand powersave userspace performance
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:1600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:powersave
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:1600000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:600000

As you can see, the CPU can scale between 600 MHz and 1600 MHz.
The governour is "powersave", but scaling_cur_freq constantly stays at 1600
MHz. In principle the powersave governour should now scale it down to 600 MHz,
but it does not.

Interestingly, when I then switch the scaling governor to "performance" (or any
other value than powersave) and then directly back to powersave, it then
suddenly does work as designed and scales the CPU down to 600MHz. It seems the
short change in the governor triggers start of the scale-down.


-- 
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.

             reply	other threads:[~2008-01-07 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 21:11 bugme-daemon [this message]
2008-01-07 21:12 ` [Bug 9708] powersave governor does not scale down when power gets connected bugme-daemon
2008-01-08 11:46 ` bugme-daemon
2008-01-08 18:51 ` bugme-daemon
2008-01-09  9:41 ` bugme-daemon
2008-01-09 20:40 ` bugme-daemon
2008-01-09 20:47 ` bugme-daemon
2008-01-23  0:43 ` bugme-daemon
2008-02-01 13:32 ` 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-9708-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.