Debug Playbook for Low-Power Verification Debug focuses on debug turnaround time, escaped LP bug count, and reproducer quality. 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 — Low-Power Verification Debug
debug turnaround time, escaped LP bug count, and reproducer quality regressed
|
reproducible in same sequence?
/ \
no yes
| |
stimulus drift intent mismatch or
testbench issue implementation bug
/ \ |
power checker crossing/strategy audit
state model + waveform timelineFreeze failing RTL, UPF, PMU sequence, and implementation tags.
Identify the first failing transition and affected crossing.
Classify issue: policy binding, sequencing, or physical realization.
Prove mechanism with one reduced reproducer.
Patch smallest owner-controlled fix.
Re-run focused checks then full LP regression matrix.
LOW-POWER REVIEW MEMO — Low Power Verification / Low-Power Verification Debug
1. Symptom
- Watched metric: debug turnaround time, escaped LP bug count, and reproducer quality
- Failing transition: <state_from -> state_to>
- Failing crossing/domain: <source -> destination>
- Revision tags: <RTL, UPF, PMU sequence, implementation>
2. Mechanism hypothesis
- Primary mechanism: LP debug correlates waveforms, power-state logs, and UPF policy decisions to isolate sequence or intent defects quickly.
- 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: debug playbook, waveform bookmarks, and failure triage report
- Required owners: verification lead, UPF owner, PMU owner
- Final decision: fix, bounded waiver, or escalationTransition-centric verification closes LP risk better than active-mode-centric regressions.
VERIFY LOOP
transition matrix -> simulation + formal -> coverage -> closureCOVERAGE CLOSURE
state transitions covered ███████████
isolation activation █████████
retention restore paths ████████state coverage
formal LP properties
isolation coverage
LP bug triage dashboard
Coverage looked high, but one untested OFF->RUN transition hid a restore race.
Rank by transition criticality
Correlate PMU logs with failures
Escalate unproven properties
Ask: what transition evidence proves this topic is closed, and which owner signs it?
State transition context must accompany every low-power metric claim.
Intent changes require simulation, formal, and implementation re-validation.
Comparing results from mismatched UPF revisions.
Assuming static checks replace transition validation.
Shipping with aged waivers and unclear ownership.
Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 1
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 2
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 3
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 4
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 5
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 6
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 7
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 8
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 9
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 10
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 11
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 12
PATH: low-power/low-power-verification/lp-verification-debug/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>Use this pack to rehearse low-power closure on low-power/low-power-verification/lp-verification-debug/debug-playbook: transition framing, policy ownership, implementation evidence, and release confidence.
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.
Which policy object is first to deviate from intent?
Which owner can apply the smallest reversible fix?
What regression matrix proves no collateral damage?
Which waiver conditions would still block release?
LP EVIDENCE CAPSULE 13
PATH: low-power/low-power-verification/lp-verification-debug/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>LP debug correlates waveforms, power-state logs, and UPF policy decisions to isolate sequence or intent defects quickly.
Metric: debug turnaround time, escaped LP bug count, and reproducer quality
This content block can't be displayed here.
Block type: unknown
This content block can't be displayed here.
Block type: unknown
This content block can't be displayed here.
Block type: unknown