Platform v1 physical qualification

Owner-connected Wi-Fi check — 2026-09-25

**PARTIAL: Wi-Fi association, DHCP, default route, router and Internet-IP reachability PASS; DNS FAIL.** The owner connected to their router and explicitly requested this narrow check. It does not waive the retained Session A warning gate or complete Session C. Current coverage is A FAIL, B NOT_TESTED, C PARTIAL with the DNS failure below, D NOT_TESTED. No configuration, credentials, service, firmware or hardware policy was changed, and no throughput/reconnect test ran.

Installed identity is unchanged: Linux 814c2f3470566021c1a9c43037fd868de8b2df9c, Reborn 155608393f6acfc6657f2f2e23cd07d0533479c6, build Y2LINUX-PLATFORM-V1-TELEMETRY-01, rootfs 2025.02.18-platform-v1.2, retained kernel 6.18.0-y2linux-platform-v1-candidate-01. Boot ID remains 3194fa9d-2dee-4105-86f0-4021580bf8d0. Full versions match before and after. Expected image hashes are the Telemetry 01 hashes below; no whole-image readback is claimed. Host timestamps, complete commands and raw results are private in evidence-private/platform-v1-physical-qualification/20260925T154016Z-owner-wifi-check/. The owner reports connecting to the router; no other manual observation was requested. The automatic checks below have no separate manual observation.

DHCP supplied DNS server 192.168.123.1; resolv.conf names that server. The platform's DNS probe also reports failure. These checks demonstrate working Wi-Fi/IP routing and a resolver-path failure; they do not isolate whether the cause is the router DNS service, DNS packet handling or resolver behavior on Y2. No alternate DNS server was configured. Native supplicant status succeeds while the platform observer still reports Starting/supplicant_unavailable, retaining the separate intermittent query/readiness problem. Online is not accepted without DNS. No speed, sustained loss, reconnect, TLS or endurance claim follows from these eight ping replies. The next focused diagnosis is the DNS path and readiness reporting; no new image has yet been shown necessary by this check.

Before/after kernel buffers each contain 67 priority 0–4 entries: the previous 14 plus 53 display log rate-limit notices accumulated before this connection check. No new critical Oops/panic/WARN-stack/ext4-I/O signature was found during the check. Existing warning and broader physical-acceptance gates remain open.

Latest attempt: installed Telemetry 01 — 2026-09-25

Read-only follow-up on the same boot: wpa_cli ping returns PONG, status returns DISCONNECTED, and list_networks has zero network rows. No connection has been configured, so not_authenticated alone is not a demonstrated Wi-Fi defect. The three direct SSH queries took 2.08–2.12 s, while a subsequent on-device comparison using the installed command runner returned successfully in 0.118 s at a 1-second deadline and 0.012 s at 4 seconds. The observer's 1-second query deadline can miss slower responses, but this comparison did not reproduce a timeout or establish its cause. Closing health remains DEGRADED with supplicant_unavailable. No credentials, network selection or restart occurred.

Timer inspection shows four dummy per-CPU clockevents backed by the real mtk-clkevt periodic broadcast timer, broadcast mask f, 10,000,000 ns timer resolution, highres=0 and nohz=0. The retained candidate configuration has CONFIG_HZ=100 and CONFIG_HIGH_RES_TIMERS unset. This narrows the warning to the current periodic-timer limitation; it does not mean the Y2 has no working timer. Enabling high-resolution/tickless behavior or strict kernel RWX is a separate kernel validation scope. The original warning stop rule remains unchanged; continuing with named limitations requires explicit owner disposition, and software changes require a separately authorized repair pass.

Follow-up evidence: evidence-private/platform-v1-physical-qualification/20260925T152936Z-readonly-triage/. Before/after status/capabilities/health/dmesg and per-command receipts are retained. The /proc/488/stack read was unavailable; the later wchan was do_select. A single earlier D-state process snapshot does not establish a persistent hang. No new Session A workload or Session C test was activated by this diagnosis.

**Telemetry repairs PASS in this observed scope. Session A FAIL at the retained kernel-warning gate; B/C/D NOT_TESTED. No physical or endurance promotion.** The owner installed the corrective image, then authorized continuation of the original qualification. No source, firmware, service, radio or hardware-policy change was made by this retest. No reboot, rescue transition or workload started.

The exact installed metadata and nine file hashes match out/y2linux-platform-v1-telemetry-01-candidate/. New boot ID: 3194fa9d-2dee-4105-86f0-4021580bf8d0. Identity:

Hash comparison covers the five replacement files and four Reborn ELFs; it is not whole installed-image readback. uname -a is the exact same kernel string recorded in the earlier attempt below. The saved owner-authorized host pin and existing login key still work; the prior independent-console-verification limitation remains. Host UTC below is authoritative: device wall time is still anchored to the September 23 build floor, NTP is not established and TLS readiness is false. RTC reads August 2022; no retention claim is made.

Private evidence (mode 0700, Git ignored): evidence-private/platform-v1-physical-qualification/20260925T151959Z-telemetry01/. Every command has UTC/arguments/exit/duration/raw-output receipts. The test register supplies full source/image identity, boot ID, observation, status and limits for every attempted test and remaining gate. The original run's sealed evidence is preserved separately. All rows below use the identity/boot above.

The wakeup counter correctly reports null / command_timeout while BAT0 reports Charging and the charger wakeup source is active. The final process table contains no lingering counter reader or pm_get_wakeup_count wait. This proves the repaired observation path on this boot, not long-run collection. Health now reports actual readiness, including failures, instead of crashing. The Wi-Fi reason changes from not_authenticated to supplicant_unavailable; no service restart, password entry, AP test or radio action was performed. Its cause and end-to-end connectivity remain unqualified.

Both root and data are Ready, separate read-write ext4 mounts with the expected UUIDs and 11230000.mmc controller. On this boot they enumerate as /dev/mmcblk0p5 and /dev/mmcblk0p7; names changed with enumeration, controller and UUID identity did not. Boot fsck reports both clean. An SD device enumerates but /media/sd is unavailable; no mount/removal/benchmark was attempted.

Normal-boot markers show switch_root 9.740 s, first frame 62.785 s, and application_ready 70.058 s. Reborn PID 363, start ticks 2824 and /usr/bin/reborn match the first-frame record. Previous boot 083d4abb-a447-4ac6-a063-e8898c150bca is recorded as orderly shutdown_complete, with previous-log tail metadata retained; this is not one of the three requested controlled reboot trials. Library readiness, rescue entry/return and all input/playback checks remain open.

Snapshot: CPU 48.800°C, PMIC 45.713°C; battery 4,024,072 µV. MemTotal 952,304 KiB, MemAvailable 865,868, LOWMEM 723,952, HIGHMEM 228,352, cache 56,684, slab 11,004. Reborn RSS 23,532 KiB, 16 threads; requested PSS remains null, not zero. Frequency time-in-state counters are 20,643 / 164 / 7,214 USER_HZ ticks at 598 / 747.5 / 1040 MHz. Per-core WFI cumulative time is approximately 249.569 / 249.092 / 256.292 / 250.001 seconds. These are mixed-boot counters, not idle/playback/scan workload utilization, power savings or endurance results. No governor/OPP/voltage change occurred. ALSA hw_params is closed; no sound or XRUN-under-playback result is inferred.

The 14 kernel entries repeat the previously reviewed timer/cache, LED-node, hardening, stock p8 clipping, regulator get_mode, Bluetooth feature quirk, Wi-Fi logging and rate-limit classes. Another 31 warning-priority lines have non-kernel facility (for example raw PRI 12) and are counted separately. No new Oops/panic/WARN-stack/ext4/I/O signature was found; taint remains zero. None of these observations waives the owner's kernel-warning stop rule. See the source-backed warning review.

Latest requested result ledger

Earlier attempt: original UI candidate

2026-09-25 UTC. Owner-supervised qualification of the already-installed out/y2linux-reborn-ui-v1-candidate/, clarified by the owner after the initial identity check found a different Reborn from the original plain Platform v1 package. The owner test plan and explicit no-flash/no-build/no-production-change limits remain authoritative.

Session A: FAIL; stopped at baseline. Sessions B/C/D: NOT_TESTED. Identity metadata and installed application hashes match the owner-clarified package. Two mandatory telemetry commands fail, and kernel warning/error-priority messages trigger the owner's Session A stop rule. No physical or endurance acceptance is declared. Sessions E/F/G and unattended long runs remain unstarted and separately gated. Recommended next step: corrective software work and warning review, then repeat Session A under the resulting exact identity.

Subsequent owner-authorized telemetry repair is complete at host/ARM/image scope. Its new candidate has not been installed. This physical record describes the original image and remains unchanged in result; software checks do not supersede its failures or missing physical tests.

Identity

Authenticated identity read: 2026-09-25 14:23:49 UTC. Boot ID: 083d4abb-a447-4ac6-a063-e8898c150bca.

All installed versions JSON fields equal the clarified package metadata. The original target expected Reborn 6c8aa128550ec80addd08ef3145e9d5a846ddf2e / 0.1.0; qualification stopped at that mismatch until the owner supplied the actual package path. Metadata matching is not installed-image readback.

Local integrity: plain Platform v1 package 1,112/1,112 checksums; clarified UI candidate 133/133. UI root SHA-256: edcecfaae26b8102c071000b5d2e9e5f84626ad08e3ff5818b050174f301a044. Required Platform v1 BOOTIMG SHA-256: f7b4a950a0504a411ad72db0aac9398f04dc1ccabd6a6a0a3a7fdab198ca2622. These are expected local image hashes, not measured whole installed images. All four installed application ELF SHA-256 values match this UI candidate's manifest: reborn, rebornctl, reborn-bench, and libreborn_media.so. Installed platform cli.py and observe.py hashes also match the inspected local source; no runtime replacement was made.

Exact uname -a:

Linux y2linux 6.18.0-y2linux-platform-v1-candidate-01 #1 SMP @1764542530 armv7l GNU/Linux

Evidence and preliminary results

Private directory (Git ignored, mode 0700):

evidence-private/platform-v1-physical-qualification/20260925T141911Z-owner/

Per-command receipts retain host UTC, exact command/SSH arguments, exit status, elapsed time, stdout/stderr and limitations. test-register.json records each attempted or unexecuted test, exact source/image context, boot ID or its limits, timestamp, command, result, manual observation, status and evidence path. test-register-original-preflight.json preserves the original-target preflight. SHA256SUMS covers the final private evidence bundle.

The owner reports “i just see the main menu normal warm”. This confirms a visible main menu and subjective normal warmth only. No buttons, playback, screen cycling or cable action were requested. The annotation time is retained in owner-observations.json; an exact physical observation time was not supplied.

The initial failed SSH command obtained no boot ID. Later diagnostics are bracketed by the same authenticated boot ID through 14:36:05 UTC; the stalled status PID was identified in that boot. Device wall time was not verified and is not substituted for host UTC. No private-key contents, passwords, bond secrets, NVRAM or calibration were inspected or exported.

The new host pin was accepted on explicit owner instruction with direct USB topology evidence; it was not independently read from a device console. Authenticated SSH alone does not prove password rejection, USB-only binding, Wi-Fi exclusion or SFTP readiness. The status timeout and health exception are diagnosed below; no silent software fix or service restart has been performed.

Session A evidence and failures

All rows below use the exact UI candidate identity and boot ID above. The private receipt named in each row contains the complete command, timestamps, exit status and unabridged output. Manual observation is absent except for the display/warmth row. PASS applies only to the stated narrow observation.

The required before/after baseline commands were attempted and preserved, but the baseline is incomplete because system status and health produced no valid JSON. Direct diagnostic reads are supplemental evidence, not replacements that make the failed public commands pass. Combined shell commands retain errors even when the last command exits 0: /proc/1945/stack was unavailable, and the queried /run/y2/services.json and /data/reborn/logs/supervisor-last.json did not exist. Those absent queried paths alone do not prove a failed production service.

Confirmed telemetry defects

1. Health CLI dispatch fails. In

   cli.py, the network-check branch imports a local check inside main(). That shadows the module-level health function throughout main(). The health branch calls this unassigned local at line 197, producing the captured UnboundLocalError. Owning subsystem: platform CLI dispatch. This is independent of physical sensor health.

2. Status observation can block indefinitely.

   observe.py reads /sys/power/wakeup_count synchronously in cpu(). The actual process was sleeping in pm_get_wakeup_count with that FD open. Kernel wakeup_count_show calls pm_get_wakeup_count(..., true), which waits for active wakeup events to finish. The charger wakeup source was active. Owning subsystem: platform observation/bounding; this is not evidence that charger wake policy should be changed. Snapshot/collection paths sharing cpu() require review before dependable baseline or endurance collection. The original host timeout left its remote read process alive; that exact diagnostic process was cleaned up.

No production file, charger policy, wakeup source, service or kernel parameter was changed to bypass either defect. No software fix was implemented.

Kernel findings and stop rule

The retained before/after buffers each contain **28 priority 0–4 kernel log entries**, including repeated rate-limiting notices. These are not 28 independent crashes. There are no retained WARNING: stack reports, Oops, kernel panic, EXT4-fs error or I/O error matches; taint remains 0. Severity-coded warnings still trigger the owner's stop condition. Relevant messages include:

An early informational Temperature check failed (-61) precedes later readable CPU/PMIC temperatures; retain it without treating current thermometry as absent. Early ext4 orphan cleanup is followed by both filesystems reporting clean and zero current error counters. It is not counted as a new filesystem error. Charger log samples carry fault=0x0; this does not qualify charging. Radio snapshot reports error=0 transport_errors=0 recoveries=0; no packet-loss percentage or connection success is inferred.

No owner reboots, rescue transition, input cycle, playback, benchmark or radio test followed the warning review. Session A is incomplete and failed; no more-invasive session was started. No historical warning is silently waived.

Narrow positive observations

Boot stages on the observed boot: initramfs 0.62 s; storage discovery 0.91 s; preflight 7.54 s; fsck 9.12–9.28 s; root/data mounted 9.65 s; switch_root 9.73 s; platform start 23.498 s; services-started marker 48.485 s; first-frame readiness record 57.785 s; application-ready stage 64.718 s. These are recorded monotonic boot times, not a new cold-boot timing experiment. Actual library-ready timing and full service health remain unverified. Historical orderly-shutdown records do not count as the requested three reboot tests.

Internal eMMC is on 11230000.mmc, exposing 15,203,328 sectors. Y2ROOT is /dev/mmcblk1p5, UUID 79324c69-6e75-4801-8000-000000000101, start 166,912, length 1,679,360 sectors. Y2DATA is /dev/mmcblk1p7, UUID 79324c69-6e75-4801-8000-000000000102, start 2,104,320, length 1,638,400 sectors. Both are separate ext4 read-write mounts; /data also has nosuid,nodev. Boot fsck reports both clean; both current errors_count values are 0 before and after collection. Available space: root 360,592 KiB, data 730,824 KiB. This does not measure write durability, throughput or recovery under faults.

Instantaneous memory snapshot, KiB: MemTotal 952,304; MemAvailable 866,608; LowTotal 723,952; HighTotal 228,352; Cached 53,356; Slab 11,308. Reborn RSS/PSS, memory growth, workload CPU and frequency/WFI residency were not collected. CPU 48.500°C and PMIC 46.298°C are die-sensor snapshots, not pack temperature or a thermal-load qualification. Battery telemetry was 3,893,994 µV; configured current is not measured battery current or energy.

y2-audio-contract accepts S16 stereo 44.1-kHz constraints. It also reports direct 48-kHz constraints; the product-enabled profile remains **S16 stereo 44.1 kHz only**. S24/S32 and 88.2/96-kHz constraints are rejected. The command reports pcm_started:false; captured hw_params says closed. No playback, unsupported mode or listening test occurred.

Requested result ledger

Unexecuted checks have no command execution timestamp, measurement or manual observation. The private register enumerates these as NOT_TESTED, including all input/audio actions, all three reboots and rescue, storage/SD lifecycle, SQLite sizes, workload resource comparisons, Wi-Fi state/failure/reconnect/throughput cases and Bluetooth/SBC/AVRCP/coexistence cases. No short observation is used to infer endurance or electrical durability.

Longer collections prepared, not started

Seven ui-plan-*.json records were generated locally using:

python3 tools/host/qualify.py capture --profile wired-8h \
  --versions out/y2linux-reborn-ui-v1-candidate/metadata/versions.json

Profiles: wired 8h; Bluetooth 8h; Wi-Fi + playback; Wi-Fi + Bluetooth; scan + playback; SD cycles; USB cycles. All report network_contacted:false. No --run was used. The original plain-candidate plan-*.json files remain historical and must not be used for this differing source pair.

Execution requires corrected/verified telemetry, relevant short sessions passed, an exact versions file for the actual resulting installed pair, explicit owner approval for duration/workload, a fresh private output directory, the existing owner private-key path and the verified/current host pin. The collector does not start a workload or operate hardware. Approval for an eight-hour run has not been requested because these prerequisites have not passed.

Wired requires observed S16 stereo 44.1-kHz media at an owner-selected safe volume. Bluetooth requires a known paired/trusted peer, actual negotiated SBC PCM and listening confirmation. Wi-Fi combinations require a controlled AP and throughput peer plus proven address/route/DNS. Scan requires a declared dataset and playback workload. SD/USB cycles require scheduled manual observations; request each removal/reinsert explicitly and use disposable media for surprise removal. Record media hashes, workload, observations, collection overhead, counter changes and gaps. Preserve the same stop conditions.

Only documentation and private host evidence were written in this repository. The host's Y2 public host-key pin was updated on owner instruction. On-device cleanup only terminated the exact query started by this qualification attempt; production code, services, hardware policy and protected data were not changed. The final process snapshot confirms no leftover status query. No build, flash, production test suite, reboot or long workload was run. Validation is limited to evidence consistency/hashes, local links and git diff --check.