Repository navigation
device/husky SUSPEND-PLAN: H0b and H1 passed on the third phone; NOTES and ROADMAP leftovers - #835
Conversation
|
@derekross, H1 ran 20 minutes after H0b, same kernel and package, and passed too. I've added it as a second commit so the two results sit together; the title now undersells it, so feel free to retitle at merge.
H2, the first real s2idle with the RTC wake, is next. I'll wait for your word on these two before running it. |
The Wi-Fi and PCIe unload and reload on their own, no sleep, on the published omamobile at 82f31d3a7 with device-husky 0.1.13: all three modules gone and the bus empty after the unload; after the reload the BCM4398 back in D0 and wlp1s0 connected again in 14 s, with only the brcmfmac noise this kernel also prints at boot. H1 to H4 have not run. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
pm_test freezer, devices and platform through systemctl suspend: three successes, no failures, devices back in 69 ms, and UFS's one "dme-set: attr-id 0x4021" line after the devices and platform resumes, as on Lef's phone, with no error handler run. H2 to H4 have not run. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…ekross#243 and derekross#244 - NOTES no longer calls SUSPEND-PLAN a draft (derekross#802). - The ROADMAP Suspend row says mem_sleep read "s2idle [deep]" before kernel derekross#244 and reads "[s2idle] deep" on the published kernel (derekross#802). - The ROADMAP Time row no longer says "No RTC": the S2MPG14's RTC is rtc0 since kernel derekross#243 (asked for on that PR). - The 2026-11-15 NOTES entry records /proc/cmdline's mem_sleep_default=s2idle with mem_sleep (asked for on kernel derekross#244), and the RTC's probe lines, wakealarm and idle interrupt count (asked for on kernel derekross#243). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
6c4aa37 to
bf36d57
Compare
|
@derekross, a third commit, documentation only, picking up leftovers so they don't get lost:
I've retitled the PR to match. H2 still waits for your word. |
|
Thank you, Colin. This is a clean record: the published kernel by commit, the package version, the counts before and after, the timings from Three small changes before I merge, all so that "passed" means what the runbook's Pass lines say:
Smaller, in the same push if you like: the two result paragraphs say "over USB" but not "attended" (your PR text does); the Kernels paragraph and section 2 still say device-husky 0.1.10 where both stages ran on 0.1.13; and the H1 result says 25 s between levels where the runbook's loop sleeps 20. On the rule "one stage per go-ahead": I had said H0b could run, and H1 followed twenty minutes later in the same sitting. It was attended, on the cable, with no real sleep, and you stopped before H2, so no harm; but I meant my go-ahead per stage, and the plan should say whose it is. Please add that to section 2. For H2, two things first. #806 is merging as device-husky 0.1.14 ( |
From the review on derekross#835: - H1's status line and heading say what was not checked: touch, the display and a played haptic effect, carried into H2, whose Pass line now names them. - Section 2 names the one UFS line that is expected at resume (dme-set: attr-id 0x4021, the peer device ID ufs-exynos sets when the link comes back) and says any other UFS error is a stop. The recovery bullet, the stop conditions and H1's Pass line say the same. - Section 3's brcmfmac noise list has the two other lines the H0b run printed, which this kernel also prints at boot. - The two results say "attended"; the package versions are the ones the stages ran on (0.1.13) and will run on (0.1.14 or later, derekross#806); the H1 loop sleeps 25 s, as the run's script did, and the reconnect comment matches. - Section 2 says whose go-ahead a stage waits for. - Section 4 records systemd-analyze cat-config systemd/sleep.conf on this unit: no /etc/systemd/sleep.conf.d/, so nothing hides the package's drop-in. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
@derekross, thank you. All of it is in one commit on top:
The smaller ones: both results say "attended"; the Kernels paragraph says 0.1.13 for H0b and H1 and 0.1.14 or later for H2 to H4; the H1 loop says 25 s, which is what the run's script used, and the reconnect comment matches. On the go-ahead: understood, and sorry for running ahead. Section 2 now says it is yours, one per stage, and records that H1 ran on H0b's. For H2: section 4 has |
|
Thank you, Colin. All of it is there: the H1 status with what wasn't checked, the On the For H2: 0.1.14 is on main now and will be in the development channel after the next nightly build. Once it is installed, please read |
|
@derekross, installed and read again.
Ready for H2 on your word. I'll add the One more question: on 11-13 you asked me to hold the Omarchy 4.5 update on this phone. Is that still your advice? |
@derekross, H0b from the merged runbook ran on my unit today, attended, over USB. It passed. Documentation only: the result goes into section 4, and the status line now says H0b passed and H1 to H4 have not run.
The run
Published
omamobileat82f31d3a7,omamobile-device-husky0.1.13, 85 % and charging, slot B refilled to 3 earlier the same day. No sleep:suspend_statsread 0 / 0 before and after.prepassed (spm_lvl5, no/sys/class/nfc).modprobe -r brcmfmac_wcc brcmfmac pcie_gs201returned 0, none of the three was left inlsmod, the PCI bus was empty and nowlpinterface remained.brcmutilandphy_zuma_pciestayed loaded with no users.modprobe pcie_gs201 && modprobe brcmfmacreturned 0. Both PCI functions came back in D0, the firmware loaded, andwlp1s0was connected to the same 5 GHz network 14 s after the reload, with three pings out of three.Ignoring unexpected firmware channel, onep2pdevtimeout, onejoin ... firmware error -14before it associated,Received unexpected monitor pkt). No PCIe, AER or UFS line;running, no failed units.phy1where it had beenphy0.Next
H1 (
pm_testfreezer, devices and platform throughsystemctl suspend) is the next stage. I'll run it attended and on the cable, with slot B at two or more retries. If you'd rather see anything else first, tell me.tools/pr-check origin/main: all ok.