Scenario: Metastability Bug

What this topic teaches

Scenario: Metastability Bug focuses on closing CDC/RDC risk with mechanism-level reasoning. A rare metastability escape tests whether the engineer can distinguish random symptom from deterministic crossing design flaws. Senior signoff depends on proving behavior with targeted evidence, not just clearing tool warnings.

The senior-engineer question

When root-cause depth, containment plan clarity, debug sequencing regresses, can you classify the hazard, identify accountable owners, and choose the smallest fix or waiver backed by evidence?

CDC/RDC SIGNOFF FLOW — Scenario: Metastability Bug

crossing inventory + reset map
          |
          v
crossing classification (level/pulse/bus/reset)
          |
          v
structure + protocol + reset checks
          |
          v
critical issues + waiver review
          |
          v
fix / validate / regress / signoff

Picture the crossing behavior

Draw the behavior before touching tools. These visuals are the expected whiteboard baseline for reviews and interviews.

Metastability escape anatomy

rare field failure
  -> thermal/voltage stress
  -> settle window collapse
  -> bad sample observed

Crossing sequence

CROSSING FLOW — Scenario: Metastability Bug

source clock domain -> launch signal -> crossing structure -> destination sample
      |                    |                 |                    |
   source FF           protocol           sync / fifo         destination FF

Key metric: root-cause depth, containment plan clarity, debug sequencing

Ownership layers

CDC/RDC OWNERSHIP LAYERS — Scenario: Metastability Bug

layer                 owns                            common failure
------------------    -----------------------------   -----------------------------
design intent         crossing architecture           wrong topology selected
protocol semantics    req/ack, fifo, ordering        liveness/deadlock bugs
reset behavior        assert/deassert sequencing      boot instability
analysis setup        tool rules + waivers            false confidence
signoff governance    risk acceptance + dashboard     stale critical waivers

Evidence to collect

• Primary metric: root-cause depth, containment plan clarity, debug sequencing.

• Primary artifact: failure report, crossing path analysis, fix validation plan.

• Owners to involve: candidate, CDC owner, DV lead.

• At least one reproducer tied to mode/reset/traffic context.

• Decision record: fix, waive, or escalate with rationale.

Ownership map

OWNERSHIP MAP — Scenario: Metastability Bug

artifact                  owner
----------------------    -------------------------
design intent           candidate
verification evidence   CDC owner
signoff decision        DV lead

Every open CDC/RDC issue needs one accountable owner before waiver or fix.

Subpages in this topic

Each topic includes mechanism, I/O contract, metrics, debug, worked example, pitfalls, interview drills, checklist, theory, design tradeoffs, expanded case study, walkthrough, comparison matrix, software view, and silicon impact.

Key takeaways

• Classify crossing/reset hazards before proposing fixes.

• Pair structural results with protocol/reset behavioral proof.

• Treat waivers as bounded risk contracts, not cleanup shortcuts.

Common pitfalls

• Mass-waiving warnings near tapeout.

• Assuming local IP cleanliness guarantees SoC behavior.

• Skipping reconvergence and reset stress after CDC fixes.

Scenario debrief

Score each response on mechanism clarity, evidence quality, and signoff decision discipline.

INTERVIEW FLOW

classify -> explain mechanism -> propose fix -> state regression

PRACTICE SCORE

session1 62%
session2 78%
session3 89%

Debrief prompts

1. Which crossing class or reset dependency failed first?

2. What evidence changed your decision?

3. Fix, waive, or escalate and why?

Key takeaways

• State crossing class, assumptions, and owner with every issue.

• Run structural and dynamic regressions after each fix.

Common pitfalls

• Treating all warnings as equivalent risk.

• Waiving issues without containment evidence.

• Skipping reset and reconvergence stress after CDC fixes.