Repository navigation
device/tegu MODEM-PLAN: the 9a sleeps with the modem up on a test kernel with the sleep guard (2026-11-13) - #758
Conversation
…nel with the sleep guard (2026-11-13) The results of the day and the night on a test kernel with linux-omarchy-mobile#232, the maintainer's two patches from its review and the sleep guard turned on for zumapro: a refusal no longer costs the phone service, 299 of 300 sleeps in one boot were entered and woke with the modem registered, and what is still open (one hang at a link power-up while awake, RTC alarms that come early or late, the route change of derekross#750, calls and texts during a sleep). The series script that ran is added to device/tegu/bringup. AGENTS.md gets one sentence; the rule for the daily kernel is unchanged.
… nothing by hand (2026-11-14) 30 of 30 requests entered with omarchy-mobile#556's phone-service package and follow_screen on: sitd told the modem the screen state itself, the sleep hook ran each time, and the route change that was derekross#750 is part of derekross#556 now.
…e stale call (2026-11-14) Four calls and two texts that arrived in a sleep each woke the palmtop and reached the phone service within a second. One call was left as ringing-in (derekross#729), and with follow_screen on that kept the modem busy and the palmtop awake.
# Conflicts: # AGENTS.md
# Conflicts: # AGENTS.md
|
Thank you for writing this up, and for putting the series script in the tree. The comparison boots are what make the record useful: the same day, without the guard, the modem was lost at the first sleep with the link down, and with the guard a refusal costs nothing and 299 of 300 sleeps came back with the modem registered. The hang at a link power-up while awake is written up honestly too. Before I can take it, three things.
The facts in the section match your reports on #232; I checked the counts and the hang against them. When these three are in, I'll merge it. |
…outside the rule; where data was checked The plan now says plainly that the 2026-11-13 and 11-14 sleeps with the modem up ran outside the rule in AGENTS.md, with their start times, and that the rule stands until the maintainer decides otherwise. For the night and the package runs it says where mobile data was checked (at the end, with Wi-Fi the first route), adds the night's count of "Reserve doorbell interrupt" and "PCI not powered on" lines (1,205 and 1,142, with data answering at the end; the daily kernel logs the same line awake with no sleep), and lists a run in the shape that lost data on the 7 Pro under what is left. The AGENTS sentence takes the maintainer's wording, so it doesn't go stale now that derekross#258 has merged. The series script checks data 5 s after every wake (a ping and a DNS query sent out of the bearer's interface), takes WIFI=off for runs with the bearer as the only route, refuses to start and stops when the palmtop isn't charging, and counts the doorbell lines at the end.
|
Thank you. All three are in (4f17cba, on today's main).
|
…m up under derekross#809 The maintainer agreed on derekross#809 that on the owner's palmtop these runs may be unattended, on the charger, each boot ending in a reboot and a new kernel's first run short, so the section says which rule applies from 2026-11-15.
|
Following your decision on #809, the section now says that from 2026-11-15 the owner's palmtop runs these under #809's terms (unattended allowed, on the charger, each boot ending in a reboot, a new kernel's first run at most 10 sleeps), and that every other 9a keeps the AGENTS rule (bb41d09). The 11-13 and 11-14 runs stay recorded as outside the rule they ran under. |
…nd every wake One line before each request and around each data check: the FMT and raw queues, the wake lines, pcie_powered_on and reserve_doorbell, each pktproc queue's fore/rear and pass, and the mif_cp2ap_msg count, read as the 7 Pro's M6-D recorder reads them, so a 9a wake that loses data says which path stopped.
|
Thank you for turning all three round so quickly, and for being plain about the rule in the plan: the start times are there, the AGENTS sentence is in on top of my correction, and the data check after every wake with Before I merge, two things, and the second one before tonight's run:
One correction on my side, not a request: part of what I asked in point 2 last time is out of date. I asked for the "Reserve doorbell interrupt" and "PCI not powered on" counts and for timer wakes. Today's runs on my 7 Pro found the doorbell clear in the failed state, and the failing wake was the modem's own, not the alarm's. What marks the failure is the bearer the modem lists. So the check that matters is data over Tonight's run with #817's package, ten sleeps first, on the charger, is exactly the run I'd like, under #809's terms. The CPIF reads haven't been taken after a wake on the 9a yet, so that first short run is their check too. AGENTS.md doesn't carry #809 yet; I'll add the exception for your palmtop in a change of my own, so your sentence can stay as it is. |
# Conflicts: # AGENTS.md
|
Thank you for merging main in. I checked the AGENTS resolution, and it is right: the modem-up entry is exactly as #823 left it, the exception for your palmtop and its terms included, and your sentence sits just before the exception. "Until a release carries the guard" is still true, since #258 is on the published branch but not in kernel-2026.11.15. The two points from my last comment are still open, though. The branch's
While you're in the script: N defaulting to 10 would make the short first run the one you get by accident, and a trap that turns Wi-Fi back on would cover a stopped unit. The header's 7 Pro failure is #799 (SUSPEND-PLAN M6-D), not #258. And as I wrote last time, "What this leaves" should ask for data over If tonight's ten sleeps have already run, please post the result and say they ran with the script as it is on this branch, without the UFS and oops stops. Once the two points are in, I'll merge it. |
…nd the plan has the 11-14 night and derekross#809's terms modem-sleep-series.sh now stops itself as derekross#809 says: on a new UFS error line or an oops, both read from dmesg so the check works with storage gone, besides the CP and the charger. N defaults to 10, a trap turns Wi-Fi back on however the script ends, and each data check after a wake has sitd's data-call lines from that sleep beside it. The header's 7 Pro failure is derekross#799. MODEM-PLAN lists the 11-14 to 11-15 night on push1-g716f6d8ef355 among the runs outside the rule, with its result (37 of 37 woke, rmnet0 0 of 5 with the bearer reported up, sitd 0.3.37), quotes all of derekross#809's terms, and asks for data over rmnet0 after every wake with sitd's lines, not the doorbell counts.
|
Thank you, both are in now (ad6ad0b), and tonight's ten haven't run yet, so they'll run with this version of the script.
Also in: N defaults to 10; with |
|
Tonight's first run on the test kernel, under #809 (unattended, on the charger, the boot ended in
The longer run is next, the same way. |
…e as on the charger With the pack full the charger holds it and the average current is about 0, so the check that wanted it above 0 stopped tonight's run at sleep 47 with the cable in. The battery's status now decides (Charging or Full; Discharging off the cable), with the current as before for a kernel that doesn't report it.
|
The longer runs, under #809 like the ten (unattended, on the charger, each boot ended in
The logs are on my side if you want any of the per-wake CPIF lines. |
|
The published kernel as it is, first run, under #809 (unattended, on the charger, the boot ended in
The longer run on this kernel is next, the same way. |
|
The longer run on the published kernel as it is (
So 77 of 77 sleeps woke and mobile data came back after every one on the published kernel. The awake hang at a link power-up is the open item for the modem with sleep. The run has ended. This boot ends in |
|
The awake hang at a link power-up came back twice on the published code, so it isn't a test-kernel leftover.
What the two share: the modem is up and idle, CPIF powers the link up and down about once a second, and one of those power-ups never comes back, with no oops and no UFS line. The old daily kernel ( The NV partitions read SAME after the overnight reset, and the morning one will be checked when the palmtop is back. |
|
Thank you, both points are in, and everything smaller too. The 11-14 night is in the list of runs outside the rule with its result and the sentence beside the Wi-Fi night. The script now stops on a new UFS line or an oops, read from Three things for after:
One small thing for the script, whenever you next touch it: with the charge limit holding the pack at "Not charging" on the cable, it stops as if unplugged. |
…ell to works (opt-in), with the runs on the published branch The cell's old condition was a fix for the third no-wake and a series from the published kernel as it is. Kernel derekross#247 is merged, and on derek/omamobile at 26867fc4e (derekross#224, derekross#232, derekross#247, derekross#258) 300 of 300 sleeps with a 60 s alarm woke with the modem off on the night of 2026-11-17: 296 on the alarm and 4 within seconds on the touchscreen's interrupt with nobody at the palmtop. On 2026-11-16, 86 of 86 sleeps entered with the modem up woke, each ended by the modem within 29 s, so none of those reached its alarm. From the review of derekross#846: the word is "works (opt-in)", since auto-sleep ships off on the 9a (omamobile-device-tegu doesn't install /usr/share/omamobile/auto-sleep-default); the cell says again that a new sleep test runs attended first and that the modem's inhibitor stays, the owner's palmtop under derekross#809 excepted; and it cites merged notes, not derekross#758's comments. MODEM-PLAN gains the 2026-11-16 section: the runs on the test kernel and on the published branch under derekross#809's terms, the route finding that became derekross#837, and the palmtop hanging awake twice at a power-up of the modem's link (once between the sleeps of a series, once in everyday use with Wi-Fi connected), with the NV check after each. The Modem cell names those hangs. SLEEP-PLAN's S1 table gains a row for the 86 modem-up sleeps and one for the night's 300, and its status line is brought up to date.
Docs and one bring-up script, no package: the 9a's results for sleep with the modem up on a test kernel with linux-omarchy-mobile#232, written into tegu's MODEM-PLAN so the device page has something to point at when #232 lands.
What
device/tegu/MODEM-PLAN.md: a new dated section after the 11-09 one, "Suspend with the modem on, with the sleep guard". On a test kernel (2db2bc35beecplus kernel device-panther 0.1.3: USB comes back after a replug, and the battery plan #247, omamobile-omarchy 0.1.23: no launch toast for a desktop entry that runs omarchy-shell #232's four commits, your 6.1 and 6.2 from its review, and.sleep_guard = truefor zumapro): a refusal no longer costs the phone service (14 refusals under a ping, 273 of 273 and 200 of 200 replies); 3 of 3 and 19 of 20 sleeps entered with the data service stopped; every request refused with Wi-Fi connected and the data service as on main (the route interaction that omamobile-modem-sit 0.3.37: the cellular default route steps aside for a system sleep #750 addressed, now part of omamobile-modem-sit 0.3.37, omamobile-modem 0.1.25, device-cheetah 0.1.56: suspend with the modem online (M6) #556); and overnight 300 requests in one boot, 299 entered and woke, 1 refused, the modem registered and the phone service answering after every one. A second commit adds the run with omamobile-modem-sit 0.3.37, omamobile-modem 0.1.25, device-cheetah 0.1.56: suspend with the modem online (M6) #556's own package andfollow_screen = yes(2026-11-14): 30 of 30 entered with nothing done by hand. Also what is open: one hang at a link power-up while awake on that build, RTC alarms that came 30 s early or late now and then, and what wasn't tested (a call or a text during a sleep, a sleep of hours, off the charger). The status table's Suspend row gets a pointer.device/tegu/bringup/modem-sleep-series.sh: the series script, so the next run of it is from the tree. The copy that ran logged to another file and didn't check thatrtcwakearmed the alarm; this one does, and has not run in exactly this form.AGENTS.md: one sentence in "Suspend with the modem on". The rule for the daily kernel doesn't change: nothing here is published.The owner was not at the palmtop for these runs; he has told me to run them without him, and the section says so.
Tested
tools/pr-checkandtests/allpass; the script passesbash -nand shellcheck. The numbers are from the runs' logs, and the kernel-side detail is on linux-omarchy-mobile#232.