Repository navigation
omamobile-audio tests: stage c9's jump comes after the watchdog's first reading - #150
Conversation
…st reading The stage c9 jump test still raised the estimate 0.4 s after starting the watchdog, so on a slow runner the watchdog took the raised value as its baseline and never muted (seen on derekross#145). It now waits for the watchdog's start line, as the other jump tests do.
|
Thank you, @W4HO-ham. This is the right fix, and thanks for tracking the red check on #145 back to this package instead of retrying it. I checked it against the watchdog: it logs its No version bump needed, I agree: One optional thought, not needed for merge: this block is now a third copy of I'll merge this as it is. After that #145 needs a new push (or a close and reopen) to pick it up, because re-running its old CI run reuses the old merge commit. |
The 9a's GNSS cell goes from "no" to WIP: a position fix on 2026-10-30 and Omarchy's Location switch serving it on 2026-10-31, started by hand (46 of 52 GGA sentences fixed, 9-13 satellites, first fix about 80 s after a client connects). It needs kernel #150 (merged) and #114, and a session lasts as long as the modem's PCIe link, one to five minutes, which is the open item. The record lands with #202.
…ss#150 alone fixes GNSS The maintainer asked whether the CRC improvement holds with the SPI flush fix alone at the bootloader's drive 0. It does: 50 of 53 GGA fixed, every received frame at bit offset 0 with a valid CRC32, the same as at drive 3. Kernel derekross#151 is closed; the plan's cause 2, the notes and the AGENTS gotcha now say so, and the gotcha keeps the lesson: one change per boot, and check whose pins they are first.
…of 10-31 Both NOTES entries kept, and the 10-29 bullet no longer credits drive 3. The status line and the script headers drop "resolved", linux-omarchy-mobile#150 is merged, derekross#150 and derekross#151 are written in full, HOLD=1 is the attended default, and the link section has today's substate result.
… rounds L-348 to L-361: shared drivers judged against every int-line user (#150), board pins against every stock user (#151), ownership flags under the consumer's lock (#152), /chosen children and Google's panel constants (#154), same-day notes PRs on one device (#208/#209), merge simulations for DEVICES rows, ours included (#165), stacked PRs that merged main (#115/#117), titles behind renumbered versions, a contributor merge that dropped the PR (#99), smoke package lists as provenance and "owner-authorized" writes (#200), promised fixes and named tags checked on the remote (#153/#157/#158), and file swaps into old packages (#193). C-23 (usbc-deadman's device scope, kernel #107) and C-24 (BNEP in a lynx-only fragment, #98). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 9a's GNSS gets a position fix: up to 13 satellites used, HDOP 0.8-1.2, GPS, Galileo, BeiDou and GLONASS tracked, CHPP clean. Two kernel fixes did it: spi-s3c64xx's FIFO flush order (kernel #150) and SPI21's pinctrl (kernel #151). With them stock's SPI configuration works and the byte swap is done in gnss_spi. MODEM-PLAN gains a "G3, resolved" section (causes, configuration, the link-hold answer, what's left); tegu-gnss-start now defaults to HOLD=0, with HOLD=1/2 kept as diagnostics, and three later sessions went through omamobile-gnss 0.2.5's start with the modem link left to cycle. AGENTS gains the flush-order and missing-pinctrl gotchas and the keep_link_up rule. NOTES gets a dated entry, and the run kit's bring-up overlays and session script are recorded, each marked bring-up only. Nothing locating the owner is recorded. Maintainer edit at merge: the Location paragraph no longer counts omamobile-gnss 0.2.5's hang marker as a safety net for the hand drop-ins, which replace the package's start and write no marker. Closes #202 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…p 7) Three rounds on the palmtop: the witnessed stop passed (the first shutdown with the CP up to end in success), then two watchdog resets with the modem up, traced to the owner's sleep-test kernel lacking kernel derekross#172's PERIC0 gate fix and kernel derekross#150's SPI flush order. The latch behaved as designed through both: kept after the reset, moved aside once, held after the second.
…p 7) Three rounds on the palmtop: the witnessed stop passed (the first shutdown with the CP up to end in success), then two watchdog resets with the modem up, traced to the owner's sleep-test kernel lacking kernel derekross#172's PERIC0 gate fix and kernel derekross#150's SPI flush order. The latch behaved as designed through both: kept after the reset, moved aside once, held after the second.
…st reading (derekross#150) The stage c9 jump test still raised the estimate 0.4 s after starting the watchdog, so on a slow runner the watchdog took the raised value as its baseline and never muted (seen on derekross#145). It now waits for the watchdog's start line, as the other jump tests do.
) The 9a's GNSS cell goes from "no" to WIP: a position fix on 2026-10-30 and Omarchy's Location switch serving it on 2026-10-31, started by hand (46 of 52 GGA sentences fixed, 9-13 satellites, first fix about 80 s after a client connects). It needs kernel derekross#150 (merged) and derekross#114, and a session lasts as long as the modem's PCIe link, one to five minutes, which is the open item. The record lands with derekross#202.
… rounds L-348 to L-361: shared drivers judged against every int-line user (derekross#150), board pins against every stock user (derekross#151), ownership flags under the consumer's lock (derekross#152), /chosen children and Google's panel constants (derekross#154), same-day notes PRs on one device (derekross#208/derekross#209), merge simulations for DEVICES rows, ours included (derekross#165), stacked PRs that merged main (derekross#115/derekross#117), titles behind renumbered versions, a contributor merge that dropped the PR (derekross#99), smoke package lists as provenance and "owner-authorized" writes (derekross#200), promised fixes and named tags checked on the remote (derekross#153/derekross#157/derekross#158), and file swaps into old packages (derekross#193). C-23 (usbc-deadman's device scope, kernel derekross#107) and C-24 (BNEP in a lynx-only fragment, derekross#98). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
) The 9a's GNSS gets a position fix: up to 13 satellites used, HDOP 0.8-1.2, GPS, Galileo, BeiDou and GLONASS tracked, CHPP clean. Two kernel fixes did it: spi-s3c64xx's FIFO flush order (kernel derekross#150) and SPI21's pinctrl (kernel derekross#151). With them stock's SPI configuration works and the byte swap is done in gnss_spi. MODEM-PLAN gains a "G3, resolved" section (causes, configuration, the link-hold answer, what's left); tegu-gnss-start now defaults to HOLD=0, with HOLD=1/2 kept as diagnostics, and three later sessions went through omamobile-gnss 0.2.5's start with the modem link left to cycle. AGENTS gains the flush-order and missing-pinctrl gotchas and the keep_link_up rule. NOTES gets a dated entry, and the run kit's bring-up overlays and session script are recorded, each marked bring-up only. Nothing locating the owner is recorded. Maintainer edit at merge: the Location paragraph no longer counts omamobile-gnss 0.2.5's hang marker as a safety net for the hand drop-ins, which replace the package's start and write no marker. Closes derekross#202 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The stage c9 test "watchdog: in stage c9 a 15 C jump of the estimate mutes" still raised the coil temperature estimate 0.4 s after starting the watchdog. On a slow CI runner the watchdog hadn't taken its first reading by then, used the raised value as its baseline, saw no jump and didn't mute. That's the failure on #145, which doesn't touch this package.
It now waits for the watchdog's "watching" line and then 0.3 s, with 60 iterations, the same as
jump()already does for the other jump tests since #107. Test-only, so no version bump.test/allpasses four times out of four locally.