Repository navigation
device/husky: a suspend runbook before the first attended test - #724
Conversation
|
@derekross, one more 8 Pro question while you're here, separate from the runbook: should a husky install take today's Omarchy 4.5 update yet? My unit is showing "Omarchy 4.5.0-3 is ready" (stable channel; it has
Is it fine to update a husky phone now, or should I set |
|
Thank you, Colin. This is the runbook I asked for, and more: the three points with what your unit actually shows, the rest of what the 7 Pro and the 6 Pro needed, the wake sources and inhibitors, and a clear line on what it leaves for later. I checked the facts I could against the trees: I'd like to hold this plan to the rule we keep for the Pixel 9a's sleep tests, since zuma and zumapro are close and the 9a's history is the only warning we have. A few changes before I merge it:
Small ones: H3's Your questions:
With those changes in, I'll merge the plan, and H1 can run when you're at the phone. |
|
@derekross, @gitColinX, the kernel and the first suspend runs on an 8 Pro, since the record needs them, and one correction to how they were described on #642. The kernel is s2idle was selected once per boot by hand, The runs, all on 2026-11-10 in one boot (
Not tried: an RTC wake (there was no RTC device) and What the five kernel logs I saved (the I didn't record the NFC state during these runs. Nothing on that phone sleeps by itself (the omamobile-sleep toggle is off), and I never used |
|
@derekross, @gitColinX, one more result for the recovery details, from an 8 Pro on The last lines of that boot's journal, on 2026-11-12 after about 22 hours of uptime: Nothing came after that. I don't know why upowerd asked: its policy on this phone acts at 2 %, but I don't have the battery level for that moment. It is the kind of case you described on #244 as a battery-critical suspend that went to The phone showed nothing at all afterwards, no charging animation, no heat, and Power + Volume Down did nothing. What got it out was a forced restart: Power + Volume Up for 30 s (the combination Two details for the runbook. In the bootloader slot B's retry count was 0 and the current slot had already switched to A (I posted the readings on #252), so read the count before the first boot after a recovery like this. And I have put #656's |
- Every stage sleeps through systemctl suspend, with the RTC armed through /sys/class/rtc/rtc0/wakealarm; H1's pm_test too. Pass lines read suspend_stats and the journal's PM: suspend entry/exit. - H4 is attended for all ten cycles; nothing in the plan is unattended. - New H0b: unload and reload Wi-Fi and its PCIe host with no sleep. The pre helper stops unless the modules are gone. - Recovery: sysrq b over SSH for a dark phone that still answers, the buttons otherwise, then the next boot's ext4 recovery; refill slot B to 3 before H0b and below two retries; what slot A holds and what a fallback there does. - The RTC check was rtcwake -m on (awake); <user>@ in H3. - H0b to H4 run on the published omamobile at 82f31d3a7. - Results: Lef's runs and kernel as he reported them on derekross#724, and this unit's unplanned critical-battery suspend of 2026-11-13. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@derekross, thank you for the careful review. All of it is in the new commit:
The small ones: H3 uses Kernel: Brett's #157 and #158 merged, so H0b to H4 now run on the published Results now has @Somnius's runs and kernel as he reported them here, with his correction to #642. It also has one unplanned event on my unit: off the charger overnight, at 04:25 UPower's critical-battery action suspended the phone ( |
|
Thank you, Colin, and thank you for answering everything in one push. I went through it point by point: every stage now sleeps through One thing before I merge:
Smaller ones, none blocking:
One merge note: #741 changes the ROADMAP row right below your Suspend row, so whichever of the two lands second gets a conflict there. Keeping both rows as each pull request has them is the whole resolution; if #741 goes in first, a rebase with that is all it needs. On UPower: both 8 Pros have now had a critical-battery suspend that didn't come back. I'll think about whether husky should power off at a critical battery, as the 7 Pro does since device-cheetah 0.1.55, before H4 rather than after; that doesn't hold this plan up. With H4 fixed, I'll merge it, and H0b can run when you're at the phone. |
Derek asked on derekross#656 for a short runbook in device/husky before an attended suspend test on an 8 Pro: Wi-Fi across sleep, UFS spm_lvl 5, NFC not polling. SUSPEND-PLAN.md has husky's read-only state for each (no sleep hook, so every stage unloads Wi-Fi and the PCIe host; spm_lvl 5 at boot; no NFC driver bound), the rest of what cheetah and raven needed (s2idle only, no cpuidle on husky), recovery, and four stages: pm_test dry runs, one RTC-woken s2idle, systemctl suspend woken by Power, ten cycles. Nothing in it has run on this unit yet. The ROADMAP Suspend row and UFS-PLAN U6 point to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Every stage sleeps through systemctl suspend, with the RTC armed through /sys/class/rtc/rtc0/wakealarm; H1's pm_test too. Pass lines read suspend_stats and the journal's PM: suspend entry/exit. - H4 is attended for all ten cycles; nothing in the plan is unattended. - New H0b: unload and reload Wi-Fi and its PCIe host with no sleep. The pre helper stops unless the modules are gone. - Recovery: sysrq b over SSH for a dark phone that still answers, the buttons otherwise, then the next boot's ext4 recovery; refill slot B to 3 before H0b and below two retries; what slot A holds and what a fallback there does. - The RTC check was rtcwake -m on (awake); <user>@ in H3. - H0b to H4 run on the published omamobile at 82f31d3a7. - Results: Lef's runs and kernel as he reported them on derekross#724, and this unit's unplanned critical-battery suspend of 2026-11-13. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
From the second review on derekross#724: - H4 runs pre before each of its ten cycles: after reloads Wi-Fi and the PCIe host, so cycles 2 to 10 would otherwise sleep with them loaded. - Section 4 has Lef's 2026-11-12 critical-battery suspend into deep on device-husky 0.1.9 (91 % afterwards, slot B at 0 and the slot on A). - The ROADMAP Suspend row says testing, with Lef's runs and the two suspends that didn't come back, and names an owner. - UFS-PLAN U6 no longer says system suspend has run on neither Tensor G3 nor G4, next to the line that says Lef's runs took UFS through it. - SUSPEND-PLAN.md loses an executable bit it had picked up. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
74eae0d to
1aa2a55
Compare
|
@derekross, thank you. All of it is in the new commit at the top of the branch, now on today's
The rebase over #741 conflicted only on the ROADMAP row below Suspend, and I kept both rows as you said. I also dropped an executable bit the plan had picked up on its way from Windows. On UPower at a critical battery: my unit has run flat twice more since, unplugged overnight (about 97 % to 4 % by morning, still with no sleep). So I'd welcome husky powering off at 3 % as the 7 Pro does, once power off itself is fixed (#578). I'm happy to do that device-package change when you decide. |
|
Thank you, Colin. That's everything: H4 now runs One small thing for later, not for this PR: the ROADMAP row says "testing" while the matrix in DEVICES.md still says "no" for the 8 Pro's suspend, and Lef's eight runs were on a local kernel. A "(on a local kernel)" in the row would make that clear; the matrix can move once H0b to H4 have run on the published one. On UPower at a critical battery: thank you for the offer. I'll come back to it once power-off works (#578). I'm merging this now. H0b can run whenever you're at the phone. |
From the review on derekross#802: the NOTES entry says the 11-13 critical-battery suspend didn't come back, and names /sys/power/mem_sleep for "[s2idle] deep", since older notes quote "s2idle [deep]". From the review on derekross#724: the ROADMAP Suspend row says Lef's runs were on a local kernel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross, this is the short runbook you asked for on #656 before anyone runs an attended suspend test on an 8 Pro. It is documentation only, and nothing in its stages has run on my unit yet.
What's in it
device/husky/SUSPEND-PLAN.md, on the model of cheetah's and raven's plans:-g755b5d1c5532, device-husky 0.1.10):unmount-fuseinsystem-sleep/), and whether brcmfmac's D3 handshake works on zuma is unknown. So every stage unloadsbrcmfmac_wcc brcmfmac pcie_gs201first and reloads after, as raven's second battery run did.spm_lvl5 at boot,rpm_lvl3; checked again before every stage./sys/class/nfc; checked before every stage, and a bound driver stops the test.freeze, nevermem); no cpuidle on husky (current_drivernone), so these stages test sleeping and waking, not battery life.suspend-offis set, so the unit has never slept on its own.pm_testfreezer/devices/platform; H2 onertcwake -m freeze -s 30; H3systemctl suspendwoken by Power (Lef's omamobile-sleepd: notice a resume when logind says so, not at the next poll #642 path); H4 ten cycles. Each is attended, on the cable, and one per go-ahead.omamobile-sleephook (raven's, in unload mode first), auto sleep, NFC with its driver bound, the modem, the AoC, SYS_SLEEP.The ROADMAP Suspend row and UFS-PLAN U6 now point to it. U6 said its runbook would come after U5; I wrote it before, since Lef's
systemctl suspendruns (#640, #642) already took UFS through system suspend atspm_lvl5. If you'd rather keep U5 first, I'll put that order back.Questions before I run H1
husky-test-20261109-t1tag plus the RTC commits (AGENTS: a plugin's link in ~/.config/omarchy/plugins outranks the package #243), because plainomamobiledoesn't have the GPU and DVFS series yet (tools/power-ab: a systemd suspend mode, and a gauge without charge_counter #157, tools/extract-vendor-firmware: the Pixel 9a's firmware #158). Is that kernel fine for these stages, or do you want them onomamobileitself?@Somnius, your #640 and #642 runs are credited at the top as the first s2idle on an 8 Pro. If you have the kernel you ran them on, I'd add it to the Results section.
Checks
tools/pr-check origin/main: all ok.