Skip to content

AGENTS: on the 9a too, a modem profile restarted in the same boot resets the palmtop - #154

Merged
derekross merged 2 commits into
derekross:mainfrom
W4HO-ham:agents-tegu-modem-restart
Oct 30, 2026
Merged

derekross merged 2 commits into
derekross:mainfrom
W4HO-ham:agents-tegu-modem-restart

Conversation

@W4HO-ham

Copy link
Copy Markdown
Contributor

The small follow-up from #138: the rfsd restart hazard found during the GNSS night matches the raven gotcha about restarting omamobile-modem, so the gotcha now has a 9a line pointing at tegu's MODEM-PLAN G3. After the modem profile has stopped (gnssd's exit), starting it again in the same boot reset the palmtop silently, a watchdog reset with nothing in pstore. Reboot instead.

Text only; nothing runs on a phone.

…ets the palmtop

The rfsd restart hazard from the GNSS night (device/tegu MODEM-PLAN G3) matches raven's gotcha: a second start of the modem profile in the same boot ended in a silent watchdog reset. Say so next to raven's line, so the next person reboots instead.
@derekross

Copy link
Copy Markdown
Owner

Thanks for writing this down. A silent reset with nothing in pstore is exactly what the next person needs to hear about before they find out the hard way. Putting it next to the 6 Pro's line is the right place, and the wording fits the section.

This sentence points at the G3 line that #153 adds, and main doesn't have it yet. So I'll merge this right after #153 (which comes after #138), and the link will land with its evidence.

Two optional thoughts, neither needed for this PR:

  • The parenthesis (OMAMOBILE_MODEM_STAGE=rfsd) could read as "only the rfsd stage is dangerous". Something like "(the one try was in the rfsd stage)" says what you tested without narrowing the rule. Your call.
  • The package itself doesn't refuse a second start in the same boot. The start script's marker only covers a bring-up that never reached ONLINE. Your palmtop wrapper already refuses a second start. A small /run marker in the profile's start doing the same would turn this gotcha into a guard on every phone. That would make a nice follow-up whenever you have time.

Also a question, out of curiosity rather than for this PR. In the rfsd stage, the profile still starts the CP watcher (it runs before the stage check), and on the 9a an open of umts_boot0 wakes the link. With the CP already powered off by the earlier stop, could that open be what hung the SoC, like the "access while the link is down" hang in the modem gotchas? If you ever look at it again, a line in G3 would help.

The parenthesis read as if only that stage were dangerous; it was simply the stage the one try was in.
@W4HO-ham

W4HO-ham commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor Author

Took the wording: "(the one try was in the rfsd stage)" now, so the rule stays wide (e08291d). The /run marker in the profile's start is a good follow-up; I'll do it as its own small PR after #148 lands, since it touches the same package. On your question: that's a fair reading. In the rfsd stage the profile starts the watcher before the stage check, and with the CP already off the open of umts_boot0 would wake a link that has nothing behind it, which is the shape of the BAR-access hang. I haven't looked again, and I'll add a line to G3 when I do rather than guess now.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

The guard you suggested is #163 (draft until #148 lands, since it takes the next version): the profile writes a marker under /run at its first start and refuses a second start in the same boot, with a test that runs it twice.

@derekross
derekross merged commit 87281ba into derekross:main Oct 30, 2026
2 checks passed
@derekross

Copy link
Copy Markdown
Owner

Thank you. The wording now keeps the rule wide, and the line it points to ("Hazard found", in G3) has landed on main with #153, so the link has its evidence. Thanks as well for turning the follow-up into #163 so quickly. I'll look at it once #148 is in. CI is green and it merges cleanly, so I'm merging this now.

derekross added a commit that referenced this pull request Oct 31, 2026
… 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>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ets the palmtop (derekross#154)

* AGENTS: on the 9a too, a modem profile restarted in the same boot resets the palmtop

The rfsd restart hazard from the GNSS night (device/tegu MODEM-PLAN G3) matches raven's gotcha: a second start of the modem profile in the same boot ended in a silent watchdog reset. Say so next to raven's line, so the next person reboots instead.

* AGENTS: the 9a line doesn't narrow the rule to the rfsd stage

The parenthesis read as if only that stage were dangerous; it was simply the stage the one try was in.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
… 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants