Repository navigation
Conversation
|
Thank you for this. Running every testing row against a build from the shared fragment is exactly what those rows needed, and the config gaps it turned up (#227) are a real catch. Two things before it merges:
Small things: a line on how NetworkManager replaced iwd would help the next person who finds it that way. This and #180 and #202 all add their section at the top of NOTES; I'm merging #180 now, so this will need a quick rebase. |
… the bring-up leftovers found on the palmtop Each testing row was booted on the palmtop from its pull request's head with the project's config, and the entry links the results. It also records the kernel config gaps, the stale plugin links and masks left from bring-up, and that a plain fastboot flash of slot B clears its successful flag.
…id not The PERIC0 GPIO clock gate that hung the SoC under modem traffic is not the sleep hang.
…lease, how NetworkManager replaced iwd, and the slot B flash and devinfo evidence Each row names the kernel release of its boot, the NetworkManager line says how the switch was made, and a new entry records the five fastboot flashes that cleared slot B's mark and the one-byte devinfo write that set it again.
ae42a0a to
7e16472
Compare
|
Done, rebased onto main with #180 in (these two entries above the 10-30 morning):
The NetworkManager line now says how the switch was made: the mask removed, iwd disabled, NetworkManager enabled, all under a two-minute dead-man. |
The reset by the buttons kept no ramoops, and the journal ends at the suspend entry, so the next run needs a watchdog reset to keep a record.
a7d3f18 to
80f787b
Compare
…, so it can't record the hang Armed, three sleeps of three reset with ACPM no longer answering after resume; disarmed, two of two woke.
pm_wakeup_irq is the S2MPG14's line, raised by a source with no mapped child 0.6 s after entry; the RTC alarm itself fires on time. The wake counts so far may describe sleeps of about a second.
…top sleeps With an alarm set, alarm 0 latches within 60 ms whatever its due time; with none, a power key release does. So every sleep has probably lasted about a second.
…alarm One 30 s sleep with cpuidle state1 disabled on all CPUs woke on the real alarm 29 s in, so the false PMIC events come with the CPUs' power-down.
… power-down and SICD through exynos-cpupm
|
Thanks for this round. Every testing row now names its boot's release, the NetworkManager line says exactly how the switch was made (and under a dead-man), and the flash-and-mark entry gives the getvar readings and the A few things, most of which I can do at merge:
On the order: this goes first. #224 and #243 link to its anchors, #248 cites its rows, and #202 also adds its section at the top of the notes. I'll resolve that one when I merge #202, keeping both sections newest first. |
…y default, fingerprint opt-in, GNSS to testing (#248) With omamobile-device-tegu 0.2.3 the charge limit, the AoC and NFC start at boot from the package, so the Pixel 9a's Charging, AoC, Speakers/mics, Sensors and NFC cells move to "works" (on by default), and Fingerprint to "works (opt-in)", as on the 7 Pro. Each was verified on a boot of its kernel pull request's head built from the shared config fragment; the record is #244's entry, which gives each boot's uname -r. The Boot cell records the 10-31 unmark and re-mark, and GNSS moves to testing with the modem started by hand (#114, #202, kernel #172). The kernel parts are in review, as each cell says. Closes #248 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… kernel, the slot B flash and devinfo records, and S1 on the clock-fix kernel (derekross#244) The Pixel 9a notes give every testing row its kernel release and record the fastboot flash that cleared slot B's successful mark and the devinfo write made during the hold; SLEEP-PLAN adds S1 on the clock-fix kernel, the empty pstore, the watchdog-through-s2idle try and the one-second PMIC wakes (W4HO-ham). Closes derekross#244 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…y default, fingerprint opt-in, GNSS to testing (derekross#248) With omamobile-device-tegu 0.2.3 the charge limit, the AoC and NFC start at boot from the package, so the Pixel 9a's Charging, AoC, Speakers/mics, Sensors and NFC cells move to "works" (on by default), and Fingerprint to "works (opt-in)", as on the 7 Pro. Each was verified on a boot of its kernel pull request's head built from the shared config fragment; the record is derekross#244's entry, which gives each boot's uname -r. The Boot cell records the 10-31 unmark and re-mark, and GNSS moves to testing with the modem started by hand (derekross#114, derekross#202, kernel derekross#172). The kernel parts are in review, as each cell says. Closes derekross#248 Co-Authored-By: Claude Opus 5.5 <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>
…efore H2; NOTES and ROADMAP leftovers H0b (the Wi-Fi and PCIe unload and reload, no sleep) and H1 (`pm_test` freezer, devices and platform through `systemctl suspend`: three successes, no failures) ran attended on Colin's 8 Pro on the published `omamobile` at `82f31d3a7` with device-husky 0.1.13; touch, the display and a played haptic effect after H1 are carried into H2, and H2 to H4 have not run. The plan now says that the UFS `dme-set: attr-id 0x4021` line at resume is expected and not a stop, lists the four brcmfmac noise lines, names the maintainer's go-ahead per stage and device-husky 0.1.14 or later for H2 to H4, and records the sleep configuration in effect. NOTES and ROADMAP pick up the leftovers from #802 and the RTC and `mem_sleep_default=s2idle` facts from kernel #243 and #244. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Two dated entries in the 9a's notes, for the record behind today's pull requests.
Every testing row on a published-style kernel. Each was a boot of the named head, built with defconfig +
omamobile.config(+ #227) +olddefconfig, with the daily kernel pushed back afterwards:It also covers the config gaps #227 fixes, and the two driver findings: the clock-out optional-parent check, and the zuma PMU allowlist entry the camera PHY needs.
Leftovers found on the palmtop from bring-up.
~/.config/omarchy/plugins/pinned to old hand copies (AGENTS: a plugin's link in ~/.config/omarchy/plugins outranks the package #243)./etcwith iwd running Wi-Fi./etc.fastboot flashof a_bimage clears slot B's successful flag (AGENTS: on the Pixel 9a a plain fastboot flash of slot B clears its successful flag too #224).Docs only. No identifiers (checked for MAC addresses and the network's name);
tools/pr-checkpasses.