All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 10564] New: Randomly sets max freq equal to min freq
Date: Sun, 27 Apr 2008 09:11:16 -0700 (PDT)	[thread overview]
Message-ID: <bug-10564-3570@http.bugzilla.kernel.org/> (raw)

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

           Summary: Randomly sets max freq equal to min freq
           Product: Power Management
           Version: 2.5
     KernelVersion: 2.6.24/25
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@www.linux.org.uk
        ReportedBy: stonecrest@gmail.com


Dell Latitude C400
i686 Mobile Intel(R) Pentium(R) III CPU - M 1200MHz GenuineIntel GNU/Linux


Usually within 5 minutes of booting up, after the computer has been off while
I'm at work or sleeping, cpufreq will suddenly revert to the lowest freq and
remain stuck in it. Before this happens, scaling works fine. I'm using the
ondemand governor. I can reboot (the only way to fix it) and then it will
typically work fine - up until I shut down for another longish period of time
and boot up again.


Here's cpufreq debug output where it changes:
cpufreq-core: updating policy for CPU 0
cpufreq-core: setting new policy for CPU 0: 800000 - 1200000 kHz
acpi-cpufreq: acpi_cpufreq_verify
acpi-cpufreq: acpi_cpufreq_verify
cpufreq-core: new min and max freqs are 800000 - 800000 kHz
cpufreq-core: governor: change or update limits
cpufreq-core: __cpufreq_governor for CPU 0, event 3
cpufreq-core: target for CPU 0: 800000 kHz, relation 1
acpi-cpufreq: acpi_cpufreq_target 800000 (0)
cpufreq-core: notification 0 of frequency transition to 800000 kHz
cpufreq-core: notification 1 of frequency transition to 800000 kHz


$ grep "" /sys/devices/system/cpu/cpu0/cpufreq/*
/sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1200000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:1200000
800000 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:userspace
ondemand performance 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:ondemand
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupported>


Let me know if I should provide anything else, since it's easily reproducible.
It's been occurring for the last 2-3 months and is pretty much unusable in this
state, so I've been rebooting often.


-- 
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-04-27 16:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 16:11 bugme-daemon [this message]
2008-04-27 16:35 ` [Bug 10564] Randomly sets max freq equal to min freq bugme-daemon
2008-04-27 17:10 ` bugme-daemon
2008-04-27 17:14 ` bugme-daemon
2008-04-27 17:30 ` bugme-daemon
2008-04-27 17:39 ` bugme-daemon
2008-04-27 18:35 ` bugme-daemon
2008-04-27 18:38 ` bugme-daemon
2008-04-28 15:26 ` bugme-daemon
2008-04-28 18:54 ` bugme-daemon
2008-04-30 10:29 ` bugme-daemon
2008-05-03 14:41 ` bugme-daemon
2008-05-03 15:13 ` bugme-daemon
2008-05-03 16:50 ` 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-10564-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.