From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 71931] New: intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
Date: Tue, 11 Mar 2014 20:41:52 +0000 [thread overview]
Message-ID: <bug-71931-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=71931
Bug ID: 71931
Summary: intel_pstate: cpufreq: __cpufreq_add_dev: ->get()
failed
Product: Power Management
Version: 2.5
Kernel Version: 3.13.5
Hardware: IA-32
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: cpufreq@vger.kernel.org
Reporter: patrik.lundquist@gmail.com
CC: dirk.brandewie@gmail.com
Regression: No
Booting 3.13.5 on a dual socket Ivy Bridge-EP resulted in this error:
[ 0.194139] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2687W v2 @ 3.40GHz (fam:
06, model: 3e, stepping: 04)
...
[ 0.246755] x86: Booting SMP configuration:
[ 0.250935] .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7
[ 0.357648] .... node #1, CPUs: #8 #9 #10 #11 #12 #13 #14 #15
[ 0.553293] x86: Booted up 2 nodes, 16 CPUs
[ 0.557666] smpboot: Total of 16 processors activated (108850.19 BogoMIPS)
...
[ 5.210204] Intel P-state driver initializing.
[ 5.232407] Intel pstate controlling: cpu 0
[ 5.253628] Intel pstate controlling: cpu 1
[ 5.274899] cpufreq: __cpufreq_add_dev: ->get() failed
[ 5.294856] Intel pstate controlling: cpu 2
[ 5.313553] Intel pstate controlling: cpu 3
[ 5.332526] Intel pstate controlling: cpu 4
[ 5.352347] Intel pstate controlling: cpu 5
[ 5.372112] Intel pstate controlling: cpu 6
[ 5.391097] Intel pstate controlling: cpu 7
[ 5.410272] Intel pstate controlling: cpu 8
[ 5.429092] Intel pstate controlling: cpu 9
[ 5.447714] Intel pstate controlling: cpu 10
[ 5.465872] Intel pstate controlling: cpu 11
[ 5.482942] Intel pstate controlling: cpu 12
[ 5.498414] Intel pstate controlling: cpu 13
[ 5.513586] Intel pstate controlling: cpu 14
[ 5.529200] Intel pstate controlling: cpu 15
CPU 1 is alive and well but missing the cpufreq driver. The system is running
fine otherwise.
Looking closer at the problem gives that intel_pstate_init_cpu() is successful
but intel_pstate_get(), which is called right after by cpufreq, fails.
Since all_cpu_data[1] is initialized it gives that sample->freq must be zero.
So the bug should be in intel_pstate_calc_busy() which calculates sample->freq
to zero.
core_pct is likely 0 due to truncation in
intel_pstate.c:intel_pstate_calc_busy():
core_pct = div64_u64(int_tofp(sample->aperf * 100),
sample->mperf);
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-03-11 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 20:41 bugzilla-daemon [this message]
2014-03-11 23:16 ` [Bug 71931] intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed bugzilla-daemon
2014-03-12 11:18 ` bugzilla-daemon
2014-03-12 11:19 ` bugzilla-daemon
2014-03-12 20:52 ` bugzilla-daemon
2014-03-17 3:18 ` 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-71931-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.