e4557c1a46
If a user first sample a PEBS event on a fixed counter, then sample a non-PEBS event on the same fixed counter on Icelake, it will trigger spurious NMI. For example: perf record -e 'cycles:p' -a perf record -e 'cycles' -a The error message for spurious NMI: [June 21 15:38] Uhhuh. NMI received for unknown reason 30 on CPU 2. [ +0.000000] Do you have a strange power saving mode enabled? [ +0.000000] Dazed and confused, but trying to continue The bug was introduced by the following commit: commit |
||
---|---|---|
.. | ||
bts.c | ||
core.c | ||
cstate.c | ||
ds.c | ||
knc.c | ||
lbr.c | ||
Makefile | ||
p4.c | ||
p6.c | ||
pt.c | ||
pt.h | ||
rapl.c | ||
uncore_nhmex.c | ||
uncore_snb.c | ||
uncore_snbep.c | ||
uncore.c | ||
uncore.h |