From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 176411] cpufreq/cpuinfo_cur_freq reports <unknown>
Date: Fri, 07 Oct 2016 21:21:34 +0000 [thread overview]
Message-ID: <bug-176411-137361-KUupSxSdng@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-176411-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=176411
--- Comment #12 from Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> ---
Same as Doug.
./perf report --header
Error:
The perf.data file has no samples!
# ========
# captured on: Fri Oct 7 14:08:08 2016
# hostname : stravinsky
# os release : 4.8.0-1-ARCH
# perf version : 4.7.g523d93
# arch : x86_64
# nrcpus online : 12
# nrcpus avail : 12
# cpudesc : Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
# cpuid : GenuineIntel,6,63,2
# total memory : 32844308 kB
# cmdline : /usr/bin/perf record -a --event=power:pstate_sample sleep 300
# event : name = power:pstate_sample, , type = 2, size = 112, config = 0x184, {
sample_period, sa
# HEADER_CPU_TOPOLOGY info available, use -I to display
# HEADER_NUMA_TOPOLOGY info available, use -I to display
# pmu mappings: cpu = 4, intel_bts = 6, uncore_imc_4 = 17, uncore_sbox_1 = 26,
uncore_cbox_5 = 24
# HEADER_CACHE info available, use -I to display
# ========
#
No samples collected. I guess intel_pstate sched_util not called.
-Please also attach your .config
In addition do this step:
# echo -n 'file intel_pstate.c +p' > /sys/kernel/debug/dynamic_debug/control
# cd /sys/device/system/cpu/cpu1
# echo 0 > online
# echo 1 > online
Take dmesg and send output
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-10-07 21:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 14:53 [Bug 176411] New: cpufreq/cpuinfo_cur_freq <unknown> for i7 5820k bugzilla-daemon
2016-10-05 14:54 ` [Bug 176411] cpufreq/cpuinfo_cur_freq <unknown> bugzilla-daemon
2016-10-05 14:55 ` [Bug 176411] cpufreq/cpuinfo_cur_freq reports <unknown> bugzilla-daemon
2016-10-05 14:56 ` bugzilla-daemon
2016-10-05 20:39 ` bugzilla-daemon
2016-10-05 20:41 ` bugzilla-daemon
2016-10-05 22:37 ` bugzilla-daemon
2016-10-05 22:51 ` bugzilla-daemon
2016-10-05 22:57 ` bugzilla-daemon
2016-10-05 23:34 ` bugzilla-daemon
2016-10-05 23:42 ` bugzilla-daemon
2016-10-07 20:16 ` bugzilla-daemon
2016-10-07 20:17 ` bugzilla-daemon
2016-10-07 20:18 ` bugzilla-daemon
2016-10-07 21:04 ` bugzilla-daemon
2016-10-07 21:21 ` bugzilla-daemon [this message]
2016-10-08 7:06 ` bugzilla-daemon
2016-10-10 14:05 ` bugzilla-daemon
2016-10-10 14:06 ` bugzilla-daemon
2016-10-10 14:07 ` bugzilla-daemon
2016-10-10 14:09 ` bugzilla-daemon
2016-10-11 22:39 ` bugzilla-daemon
2016-10-11 23:04 ` bugzilla-daemon
2016-10-11 23:49 ` bugzilla-daemon
2016-10-12 18:03 ` bugzilla-daemon
2016-10-13 14:32 ` bugzilla-daemon
2016-10-13 17:27 ` bugzilla-daemon
2016-11-26 12:32 ` bugzilla-daemon
2016-11-26 13:34 ` bugzilla-daemon
2016-11-28 17:06 ` bugzilla-daemon
2016-12-22 2:20 ` bugzilla-daemon
2017-01-31 21:06 ` bugzilla-daemon
2017-01-31 21:06 ` bugzilla-daemon
2017-01-31 21:10 ` bugzilla-daemon
2017-04-03 23:41 ` bugzilla-daemon
2017-04-03 23:44 ` bugzilla-daemon
2017-04-03 23:56 ` [Bug 176411] cpufreq/cpuinfo_cur_freq reports <unknown>, MSI X99A SLI PLUS i7-5820K, MSI i7-5930K, MSI X99A Raider i7-5820K bugzilla-daemon
2017-04-03 23:58 ` bugzilla-daemon
2017-04-06 16:37 ` bugzilla-daemon
2017-04-07 6:58 ` bugzilla-daemon
2017-05-02 15:54 ` 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-176411-137361-KUupSxSdng@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pm@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.