From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 59821] Dell M4600 CPU cores locked at 800MHz
Date: Mon, 17 Jun 2013 17:11:13 +0000 (UTC) [thread overview]
Message-ID: <20130617171113.BDF6611FB51@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-59821-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=59821
--- Comment #6 from George B. <list1@gir.me.uk> 2013-06-17 17:11:13 ---
Created an attachment (id=105021)
--> (https://bugzilla.kernel.org/attachment.cgi?id=105021)
grep . /sys/devices/system/cpu/cpu*/cpufreq/* (CONFIG_X86_INTEL_PSTATE)
Seeing similar behaviour after compiling with CONFIG_X86_INTEL_PSTATE enabled,
except when problem occurs CPU speed will go as high as 897000 and when problem
cleared with s2ram as high as 3381000.
Also, many more values are seen in between these, whereas with
CONFIG_X86_ACPI_CPUFREQ the speed is mostly (maybe even always) either 800000
or 3200000.
--
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-06-17 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-59821-12968@https.bugzilla.kernel.org/>
2013-06-17 12:44 ` [Bug 59821] Dell M4600 CPU cores locked at 800MHz bugzilla-daemon
2013-06-17 12:52 ` bugzilla-daemon
2013-06-17 13:09 ` bugzilla-daemon
2013-06-17 13:18 ` bugzilla-daemon
2013-06-17 17:11 ` bugzilla-daemon [this message]
2013-06-20 6:48 ` bugzilla-daemon
2013-06-24 9:46 ` bugzilla-daemon
2013-06-24 9:46 ` bugzilla-daemon
2013-08-20 13:40 ` bugzilla-daemon
2013-10-14 5:14 ` bugzilla-daemon
2013-10-24 7:37 ` bugzilla-daemon
2013-12-09 8:25 ` 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=20130617171113.BDF6611FB51@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).