claude-noether
62a6f88abd
2026-05-16 bisect found that linux-rk3588-marfrit @ f8f3ad9 (the previous baseline.ref) black-screens ampere — eDP connector reports connected/enabled/dpms On + SDDM starts + backlight on, but the panel shows no pixels. Decomposing the suspend/resume patch 0010 into 5 atomic sub-commits and reverting all of them did NOT recover display, ruling out 0010 as the offender. The 6 patches already listed in fleet/ampere.yaml's includes apply cleanly on top of v7.0-rc3 mainline and produce a kernel that boots with working display + power-off. That's the verified-working baseline, captured here. Regression source is in one of the 12 remaining commits f8f3ad9 has on top of v7.0-rc3. Top suspect: 55d1b3dcc05e "clk: rockchip: rk3588: Drop CLK_SET_RATE_PARENT from DCLK_VOP2_SRC" (touches display controller clock parent rate). Bisect campaign separately. For consumers who want a ready-to-fetch ref instead of patches-on-mainline, the verified-working tree is on git.reauktion.de/marfrit/linux-rk3588-marfrit @ ampere-minimal-devices (7c241f2e2835). No change to the includes list — same 6 patches as #8, just retargeted to a baseline they can actually be applied to. Generated-by: Claude Opus 4.7 <claude@reauktion.de>
fleet/
Per-host manifests. One YAML per fleet member opting in to kernel-agent.
Each manifest pins:
- baseline kernel tree + ref
- scope-tagged patch includes (resolved against
../patches/) - config strategy
- package naming + install mode (alongside / replace)
- verification bars (which of Bar 1..5 apply)
- build host routing
- backup target
Manifest is the single source of truth. Running state may drift; drift is informational, not blocking. ka-status reports per-host drift.