BERT, Eye Scan, and Error Analysis: Reports and Metrics

Reports and metrics

Reports and Metrics for BERT, Eye Scan, and Error Analysis focuses on BER at target confidence and eye width/height at 1e-12 or protocol threshold.. The purpose is to turn link observations into mechanism-backed actions with explicit owners and release-safe validation.

Reports should explain why BER at target confidence and eye width/height at 1e-12 or protocol threshold. moved, not simply that it moved. Require evidence that links the movement to command behavior, queue policy, PHY margin, or reliability controls.

Before/after trend

BEFORE / AFTER - BERT, Eye Scan, and Error Analysis

BER     ████████        ██
margin  ███             ██████
retrain █████           █

metric: BER at target confidence and eye width/height at 1e-12 or protocol threshold.

Evidence matrix

SERDES EVIDENCE MATRIX - BERT, Eye Scan, and Error Analysis

+-------------------------------+--------------------------------+--------------------------------+---------------------------+
| Evidence                      | Tells you                      | Does not prove                 | Next action               |
+-------------------------------+--------------------------------+--------------------------------+---------------------------+
| eye margin/miss + ACT/PRE mix    | locality and row-state cost    | lane-level capture integrity   | inspect training margins  |
| queue age + class breakdown   | fairness and starvation risk   | command legality details       | parse command timeline    |
| IEEE/OIF legality + bus timeline | timing-window pressure         | root cause by itself           | correlate with traffic map|
| eye / Vref / skew snapshots   | PHY margin and drift behavior  | controller policy quality      | pair with schedule logs   |
| CE/UE + scrub telemetry       | reliability trajectory         | immediate perf bottleneck only | map to hotspot addresses  |
+-------------------------------+--------------------------------+--------------------------------+---------------------------+

• Track p50/p95/p99 latency and effective bandwidth together.

• Include command and queue context alongside high-level counters.

• Tag reports with firmware, timing profile, and thermal state.

• Call out contradictory evidence instead of hiding it.

SerDes deep dive

Compliance fixtures, BERT/eye scan, failure signature debug, and production screening for SerDes signoff.

Concept diagram

VALIDATION DEBUG
compliance-test-fixtures -> bert-and-eye-scan -> closure

Metric graph

MARGIN TREND
healthy ██████
failing ██

Reports and artifacts

• eye margin log

• BER/FEC counter sheet

• coefficient dump

• JTOL/compliance margin report

Mini case study

A corner board failed link training after package update; isolating lane skew and PI noise restored margin.

Debug branches

• Classify failure: training, eye, jitter, deskew, or runtime drift

• Capture coefficient and margin artifacts under fixed thermal tags

• Correlate SI/PI measurements before retuning adaptation

Senior review question

Ask: which latency, bandwidth, and reliability evidence proves this SerDes 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 SerDes 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.

Report interpretation

BERTs stress links with PRBS or compliance patterns while error counters and eye scanners map margin. Eye scan sweeps phase and voltage to build two-dimensional bathtub curves. Correlating BER floors with FEC correctables distinguishes analog margin from protocol issues. SERDES inefficiency is multiplicative: one extra ACTIVATE, one unnecessary turnaround, one weak lane margin, or one refresh collision repeated across billions of accesses can dominate product tail latency and power.

Use BER at target confidence and eye width/height at 1e-12 or protocol threshold. as the opening signal, not the conclusion. A metric move only becomes actionable when paired with workload context, training traces, training telemetry, and evidence artifacts such as Bathtub curve and eye heatmap with BER confidence interval..

Compliance fixtures, BERT/eye scan, failure signature debug, and production screening for SerDes signoff. Senior review quality comes from proving a complete chain: request pattern -> link-state transition -> bottleneck mechanism -> smallest owner fix -> regression-safe validation.

For BERT, Eye Scan, and Error Analysis, reports should explain why BER at target confidence and eye width/height at 1e-12 or protocol threshold. moved: fewer row misses, lower turnaround waste, better refresh placement, or stronger lane margin stability.

Strong reports include consistency checks: scheduler narrative matches training logs; PHY narrative matches margin sweeps; reliability narrative matches CE/UE trajectories.