Debug playbook

Debug Playbook for Save/Restore Sequencing focuses on save-ack latency, restore convergence time, and wake-up failure rate. The goal is to link observed behavior to power-intent mechanism, ownership, and release risk.

Low-power debug is timeline-centric. Find the first transition deviation, then trace policy and ownership from intent to implementation.

Root-cause tree

ROOT-CAUSE TREE — Save/Restore Sequencing

save-ack latency, restore convergence time, and wake-up failure rate regressed
        |
   reproducible in same sequence?
     /                \
   no                  yes
   |                    |
stimulus drift      intent mismatch or
testbench issue     implementation bug
 /      \              |
power    checker     crossing/strategy audit
state    model       + waveform timeline

1. Freeze failing RTL, UPF, PMU sequence, and implementation tags.

2. Identify the first failing transition and affected crossing.

3. Classify issue: policy binding, sequencing, or physical realization.

4. Prove mechanism with one reduced reproducer.

5. Patch smallest owner-controlled fix.

6. Re-run focused checks then full LP regression matrix.

Review memo template

LOW-POWER REVIEW MEMO — Isolation & Retention / Save/Restore Sequencing

1. Symptom
   - Watched metric: save-ack latency, restore convergence time, and wake-up failure rate
   - Failing transition: <state_from -> state_to>
   - Failing crossing/domain: <source -> destination>
   - Revision tags: <RTL, UPF, PMU sequence, implementation>

2. Mechanism hypothesis
   - Primary mechanism: Power controllers orchestrate save, isolation, power-off, power-on, restore, and release ordering; incorrect sequencing causes functional loss or X storms.
   - Competing hypotheses: <intent mismatch, sequence bug, physical issue>
   - Missing evidence: <coverage, waveform bookmark, signoff report>

3. Proposed action
   - Minimal reversible change: <policy/sequence/implementation patch>
   - Expected movement: <coverage, violation count, transition pass rate>
   - Regression risk: wake-up timing, X-leak, IR droop, retention stability

4. Signoff
   - Re-run artifact: power-sequence timing diagram, PMU firmware sequence, and assertion report
   - Required owners: PMU owner, RTL owner, verification owner
   - Final decision: fix, bounded waiver, or escalation

Low-power deep dive

Isolation and retention are sequence-sensitive contracts, not static checkboxes.

Concept diagram

SEQUENCE

save -> isolate -> power-off -> power-on -> restore -> release

Metric graph

TRANSITION DEFECT MIX

polarity errors      ███████
late iso assertion   █████
restore ordering     ████

Reports and artifacts

• isolation crossing report

• retention list

• save/restore timing

• X-propagation log

Mini case study

A late isolation enable caused intermittent X leaks only on one PMU path.

Debug branches

• Validate control polarity

• Trace AON source

• Replay transition waveform

Senior review question

Ask: what transition evidence proves this topic is closed, and which owner signs it?

Key takeaways

• State transition context must accompany every low-power metric claim.

• Intent changes require simulation, formal, and implementation re-validation.

Common pitfalls

• Comparing results from mismatched UPF revisions.

• Assuming static checks replace transition validation.

• Shipping with aged waivers and unclear ownership.

Execution drill pack 1

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 1

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 2

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 2

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 3

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 3

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 4

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 4

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 5

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 5

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 6

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 6

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 7

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 7

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 8

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 8

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 9

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 9

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 10

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 10

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 11

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 11

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 12

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 12

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Execution drill pack 13

Use this pack to rehearse low-power closure on low-power/isolation-retention/save-restore-sequencing/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.

Transition checklist

• State transition explicitly named with legal source/target states.

• Crossing and domain ownership are mapped and agreed.

• Policy controls are traced to always-on source logic.

• Waveform bookmarks align controls with state timestamps.

Review prompts

1. Which policy object is first to deviate from intent?

2. Which owner can apply the smallest reversible fix?

3. What regression matrix proves no collateral damage?

4. Which waiver conditions would still block release?

Evidence capsule

LP EVIDENCE CAPSULE 13

PATH: low-power/isolation-retention/save-restore-sequencing/debug-playbook
STATE WINDOW: <from -> to>
POLICY OBJECT: <isolation / retention / shifter / switch>
OWNER: <name>
PRIMARY ARTIFACT: <report/waveform/formal result>
RELEASE DECISION: <close / bounded waiver / escalate>

Principal LP review addendum

Power controllers orchestrate save, isolation, power-off, power-on, restore, and release ordering; incorrect sequencing causes functional loss or X storms.

Metric: save-ack latency, restore convergence time, and wake-up failure rate