fix(node-bootc): pstore backend becomes efi_pstore — ramoops cannot survive an hcloud reset #96

Merged
pipeline-bot merged 1 commit from fix/pstore-efi-backend into trunk 2026-08-16 02:04:00 +00:00
Owner

Crash-drill finding: panic->auto-reboot->rejoin proved in 62s, but ramoops records die with guest RAM on hcloud resets. UEFI is confirmed; dropping the ramoops kargs lets compiled-in efi_pstore take the backend (EFI varstore survives resets). One-line kargs change; rides the next kernel roll; the next drill proves capture.

Crash-drill finding: panic->auto-reboot->rejoin proved in 62s, but ramoops records die with guest RAM on hcloud resets. UEFI is confirmed; dropping the ramoops kargs lets compiled-in efi_pstore take the backend (EFI varstore survives resets). One-line kargs change; rides the next kernel roll; the next drill proves capture.
The seanfarm33 crash drill (2026-08-15, worker 55d23a): deliberate
sysrq-c, panic=30, node Ready again in 62 seconds — the
panic-and-self-heal posture works. The pstore half missed: ramoops
bound correctly and the region reserved, but hcloud/QEMU resets do not
preserve guest RAM, so the record died with the reboot.

These VMs boot UEFI. Dropping the ramoops kargs lets the compiled-in
efi_pstore register as the backend; the EFI varstore persists across
resets and power cycles. Proof rides the next roll's drill.
sean force-pushed fix/pstore-efi-backend from 7ed88c15b9
All checks were successful
pipeline/ci CI green @ 7ed88c15b9c8
to 963c18a943
All checks were successful
pipeline/ci CI green @ 963c18a943fa
2026-08-16 02:02:51 +00:00
Compare
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/builder-images!96
No description provided.