Surprise Down and Link Loss Handling: Review Checklist

Review checklist

Review Checklist for Surprise Down and Link Loss Handling focuses on Surprise-down detection latency, in-flight IO drain time, and recovery success rate. The purpose is to turn memory observations into mechanism-backed actions with explicit owners and release-safe validation.

• Workload scope and SLA targets are explicit.

• Environment tags are locked and reproducible.

• First failing transition is proven by command-level evidence.

• Owner and rollback criteria are documented.

• Validation matrix covers performance, stability, and reliability.

• Owners signed: firmware owner, driver owner, platform architect, validation owner.

PCIe/CXL deep dive

RAS closure maps AER, poison, and surprise-down events to bounded containment and recovery actions.

Concept diagram

RAS ESCALATION

detect -> classify -> contain -> recover -> validate

Metric graph

RAS EVENT MIX

correctable trend   ███████
uncorrectable       ██
surprise-down       █

Reports and artifacts

• AER register dump

• poison injection log

• surprise-down timeline

• containment action record

Mini case study

Masked correctable errors accumulated until a surprise-down during peak traffic forced unplanned failover.

Debug branches

• Separate CE trend from UE containment paths

• Validate poison handling end-to-end

• Test surprise-down drain and driver recovery

Senior review question

Ask: which latency, bandwidth, and reliability evidence proves this PCIe/CXL topic is closed under real traffic?

Key takeaways

• Always tie controller and PHY counter shifts to application latency and throughput outcomes.

• Lock firmware timing profile, thermal condition, and DIMM state before comparing PCIe/CXL captures.

Common pitfalls

• Chasing peak bandwidth while ignoring p99 latency and fairness tails.

• Changing timing guardbands without separating SI noise from scheduling issues.

• Declaring closure without reliability gates, fault injection, and regression replay.

Review checklist explanation

A checklist here protects against false closure. Every item should map to a known memory failure mode.

For Surprise Down and Link Loss Handling, minimum checklist: workload scope, Surprise-down detection latency, in-flight IO drain time, and recovery success rate, artifact evidence (Link down event log, in-flight transaction snapshot, and driver recovery trace), bottleneck class, owner, rollback path, and corner-matrix validation.

If controller or firmware changed, include fairness and RAS checks. If PHY or package assumptions changed, include SI/PI and thermal guardband evidence.