From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 60211] New: intel_pstate driver missing ids for some supported CPUs
Date: Fri, 28 Jun 2013 01:13:07 +0000 (UTC) [thread overview]
Message-ID: <bug-60211-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=60211
Summary: intel_pstate driver missing ids for some supported
CPUs
Product: Power Management
Version: 2.5
Kernel Version: 3.10rc7
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@vger.kernel.org
ReportedBy: chizu@spicious.com
CC: dirk.brandewie@gmail.com
Regression: No
Running 3.10-rc7 on an i5-4200U, with either intel_pstate or the older cpufreq
drivers the CPU was stuck at 800MHz. I added the model, 0x45, to
intel_pstate_cpu_ids and frequency scaling seems to be working as intended now.
--
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-06-28 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 1:13 bugzilla-daemon [this message]
2013-06-28 4:09 ` [Bug 60211] intel_pstate driver missing ids for some supported CPUs bugzilla-daemon
2013-07-01 2:23 ` 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=bug-60211-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 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.