8d7721c775
B7A: QMI DMS time vs VNIIFTRI NTP (DMS = UTC - 0.28 s, sigma 1 ms; NITZ = DMS truncated to 1 s). B7B: a 1970 -> 2026 date -s step is harmless for the modem stack. B7C: aurora-modem probes DMS/NITZ along the start flow and steps CLOCK_REALTIME once at the first valid sample (REG registered/attached), never RTC; background SNTP check (query only) after START OK. 3/3 class-A cold boots PASS (residual +0.04/+0.36/+0.84 s), cache 14fe453a written (B7C_WRITE_VERIFIED) and verified by a normal power-on (V1, +0.26 s). Also publishes the prerequisite R2 (boot-hang / lk eMMC investigation, T4 telnet baseline that B7C builds on) and R3 (autonomous cold boot, NCM loss) material, and extends tools/publish-sanitize.py to r2/, r3/, b7/. Binary images, initramfs, busybox and raw logs stay out (see b7/*/SHA256SUMS).
627 B
627 B
B7C c2b — NOT a cold boot (operator error on my side): the board was still in lk fastboot after the c2 reset, the driver booted it at once.
RTC at boot 759 s → class B. Functional result: probes 1-4 INVALID (DMS 3229…7193 ms = modem uptime from 1980), probe 5 at REG registered/attached VALID (NITZ Δ +0.77 s) → TIME SET at uptime 23.91 s; START OK 75.9 s; SNTP check +0.453 s (best, ntp2, 40 ms RTT), verify ntp2 +0.464…+0.472 s; clock kept (< 1 s); UNSYNC kept, RTC untouched, eMMC writes 0, dmesg-errs 0. Not counted. Driver fixed: if fastboot is already present it first waits for it to disappear (power-off).