Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Puzzle Bank
  • SystemVerilog Language Puzzles25
  • Difficulty Guide
  • Full Topic Map
  • Interview-Day Tips
  • OOP & Testbench Puzzles25
  • Concurrency & Timing Puzzles25
  • Randomization & Constraint Puzzles25
  • SVA Assertion Puzzles25
  • Functional Coverage Puzzles25
  • Logic & Aptitude Puzzles25
  • Scenario & Debug Puzzles25
    • Testbench Debug Puzzles: Why Did the Test Hang?
    • Deadlock Scenario Puzzles: Objection and Phase Stalls
    • Scoreboard Puzzles: Mismatch or Ordering Bug?
    • Real Interview Rounds: End-to-End Debug Walkthrough
      • Round Walkthrough: Sequencer Waits for item_done
      • Round Walkthrough: Objection Deadlock with Clean Waves
      • Round Walkthrough: APB Reads Return Previous Data
      • Round Walkthrough: Out-of-Order Channel Mismatch
      • Round Walkthrough: Rare Parallel Deadlock
      • Round Walkthrough: End-of-Test False Fail
    • Scenario & Debug Puzzles: Tricky Q&A
  • Interview Prep: Puzzle Rounds5
  • DV Puzzle Cheatsheet
Loading lesson

‹Real Interview Rounds: End-to-End Debug Walkthrough
  1. Topics
  2. DV Interview Puzzles
  3. Scenario & Debug Puzzles
  4. Real Interview Rounds: End-to-End Debug Walkthrough
  5. Round Walkthrough: Sequencer Waits for item_done

VLSI DV Interview Puzzles · All levels

Round Walkthrough: Sequencer Waits for item_done

Live interview round: test hangs at 2.3 ms, log says seqA waiting for item_done. Walk through the full debug narrative and give the concrete fix.

On this page

    Puzzle

    Difficulty: Medium · Puzzle 1 of 6 · Topic: Real Interview Rounds: End-to-End Debug Walkthrough

    Live interview round: test hangs at 2.3 ms, log says seqA waiting for item_done. Walk through the full debug narrative and give the concrete fix.

    Code

    design.sv
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    virtual task run_phase(uvm_phase phase);
      my_item req;
      forever begin
        seq_item_port.get_next_item(req);
        if (req.err) begin
          return; // bug
        end
        drive_req(req);
        seq_item_port.item_done();
      end
    endtask

    Hint

    In interview settings, structure matters as much as correctness.

    Step-by-step solution

    Diagram
    1) Symptom: identify liveness failure (sequence blocked waiting handshake completion).
    2) Hypotheses: missing item_done path, blocked driver thread, or sequencer arbitration starvation.
    3) Instrumentation: add paired logs for get_next_item/item_done with transaction ids.
    4) Root cause: early return on req.err exits loop without item_done.
    5) Fix + validation: replace return with guarded branch that still calls item_done; rerun failing seeds.

    Answer

    Answer: Actual bug: driver returns before item_done on error path. Fix: preserve one item_done per get_next_item and keep loop alive.

    Why candidates get it wrong

    Candidates often jump straight to fix before proving which branch skipped handshake completion.

    Interviewer follow-up

    What one-line assertion would you add to catch missing item_done within bounded cycles?

    Related topics

    • Back to Real Interview Rounds: End-to-End Debug Walkthrough

    • Scenario & Debug Puzzles section

    Previous

    198 / 210

    Next: Round Walkthrough: Objection Deadlock with Clean Waves

    Up next

    Up nextRound Walkthrough: Objection Deadlock with Clean Waves

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Round Walkthrough: APB Reads Return Previous Data
    • Round Walkthrough: Out-of-Order Channel Mismatch
    • Round Walkthrough: Rare Parallel Deadlock