rr-debugger / rr-debugger/rr

AMD Assertion: 'Assertion `!counting_period || interrupt_val <= adjusted_counting_period' failed to hold'

Open
#2,834 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.7k
Forks
662
Avg merge
2d 3h
Merged PRs (30d)
2

Description

This is related to #2720 but is triggering frequently on playback; not just recording, on AMD CPUs. (Specifically threadrippers.)

Bumping the skid from 10000 to 30000 worked for Nika; but made it extremely slow.

The issue is (I'm told) that on these CPUs the PMU interrupt is fired with a variable (and often too high) latency; causing us to overshoot the bounds.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the related issue #2720 and the code path that raises the counting-period assertion during playback on AMD Threadripper CPUs. Reproduce the failure with the current skid setting and compare it with the 30000 workaround; done means playback no longer triggers the assertion without making execution extremely slow.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools, operating-systems, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.