uzbek-plus/logs/r2/t4/T4-partial.txt
q 8d7721c775 B7: add network time bootstrap and persistent B7C cache
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).
2026-10-02 20:18:25 +03:00

9 lines
951 B
Text
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

R2/T4 (2026-10-02 10:55 MSK): read-only eMMC snapshot — NOT EXECUTED on the board (no command channel).
- CH340 TX -> board RX disconnected => no UART shell input.
- Board RAM-Linux has no shell/listener over NCM; nc listeners are only ever started via UART.
- Host NCM iface enp60s0u1u2u1 has no 172.16.42.2 (sudo needs password); 172.16.42.1 and ff02::1 don't answer.
- Board's aurora-modem logged "usb0 ping lost" at 10:42:20 (same cause: host has no IPv4 on NCM) -> modem rollback (unrelated to R2).
Partial T4(b) from existing UART log logs/uart/r2t3c-20261002-102255.log (C1–C6 boots, on 480s):
- each boot: "mmc0: new HS200 MMC card at address 0001", H4G2a 3.64 GiB, "Card appears overclocked; req 177770000 Hz, actual 177777777 Hz" (benign rounding).
- 0 mmc/sdhci error, timeout, CRC, or re-tuning lines in the kernel console during C1–C6 (boot + ~5–20 s runtime only).
Not obtained: pre_eol_info, life_time, EXT_CSD[162], err_stats.