read_aperf_mperf_tsc_perf for most cpus after resume from suspend
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c, nixos
- Domain
- operating-systems, performance
Research direction
The issue names read_aperf_mperf_tsc_perf and the systemd log but no source file or test. Start by locating that function and reproducing a suspend/resume cycle on the reported NixOS and i5-12500H setup; done means the post-resume CPU read failures are explained and no longer appear, with WLT behavior checked.
Written by the indexing model from the issue text.
Description
i've a nixOS laptop with an i5-12500H cpu, after resume from suspend, I get
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 1
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 2
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 3
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 4
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 5
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 6
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 7
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 8
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 9
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 10
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 11
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 12
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 13
intel_lpmd[30687]: read_aperf_mperf_tsc_perf failed for cpu = 14
in the systemd log. the WLT state remains as WLT_IDLE, but that's probably just because its the lowest power state I set.
- Dominant language
- C
- Stars
- 235
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/intel-lpmd
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
intel/intel-lpmd#137 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
intel/intel-lpmd#125 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
intel/intel-lpmd#140 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
intel/intel-lpmd#139 ·
-
Please don't move processes out of cgroupsPossibly taken @0x484558 claimed this 37 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
intel/intel-lpmd#128 · 15 comments ·
All issues in intel/intel-lpmd
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
JS_SetPropertyInternal2 loses the value when a lazy property on the prototype runs out of memoryOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
quickjs-ng/quickjs#1852 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day