From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 53051] New: Conservative governor get's sometimes stuck at highest frequency
Date: Fri, 25 Jan 2013 19:12:28 +0000 (UTC) [thread overview]
Message-ID: <bug-53051-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=53051
Summary: Conservative governor get's sometimes stuck at highest
frequency
Product: Power Management
Version: 2.5
Kernel Version: 3.6.11
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@vger.kernel.org
ReportedBy: cem.aydin@gmx.ch
Regression: No
Created an attachment (id=91801)
--> (https://bugzilla.kernel.org/attachment.cgi?id=91801)
Zipped files as described in description.
About once a week, when booting daily, the CPU (all cores) get's stuck at
highest frequency.
Unfortunately, I can't tell exactly when this appeared but it was about during
the time, when I switched to systemd and cpufrequtils got replaced cpupower,
about half a year ago.
The kernel modules are loaded properly and the start scripts are executed. I
can not find any difference, when this occurs or when it doesn't. Exept that
the frequency is stucked at highest level of course. When this occurs I wasn't
able to set the frequency manually (by the userspace governor). Reloading the
conservative module or reexuting the (systemd) start script did not have any
effect. The only thing I can do to resolve the issue is reboot.
I use an up to date Arch Linux with the regular kernel and systemd.
Additional Infos:
proc/cpuinfo reports the wrong frequency (lowest). I think this is mentioned in
another bug. However cpupower -c all frequency-info (executed as root) reports
the correct highest frequency. I can clearly see that this is the true
frequency because the temperatures reported by sensors are almost 10°C higher
than under normal circumstances. I don't have any process that could cause the
governor to raise the frequencies. CPU usage is below 1% and load is between
0.0 and 0.05.
Hardware:
A HP Pavilion dv6 CORE i5
Attachments:
- cpupower (/usr/lib/systemd/scripts/cpupower, the start up scripts used by
systemd to set the frequencies)
- cpupower.conf (/etc/conf.d/cpupower)
- cpupower-service.txt (output from systemctl status cpupower.service)
- cpupower.txt (output from cpupower -c all frequency-info)
- journal.txt (output from journalctl -b | grep cpufreq)
- lsmod.txt (output from lsmod |grep cpufreq)
- proc_cpuinfo.txt (output from cat /proc/cpuinfo (wrong frequencies))
Please let me know if you need additional info.
Regards
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2013-01-25 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 19:12 bugzilla-daemon [this message]
2013-02-21 7:28 ` [Bug 53051] Conservative governor get's sometimes stuck at highest frequency bugzilla-daemon
2013-04-02 14:05 ` bugzilla-daemon
2013-04-25 2:17 ` bugzilla-daemon
2013-04-25 2:17 ` [Bug 53051] Conservative governor get's sometimes stuck at highest frequency - HP Pavilion dv6 CORE i5 bugzilla-daemon
2013-05-05 13:48 ` bugzilla-daemon
2013-05-12 15:56 ` 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-53051-12968@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox