diff options
| author |  sommerfeld <sommerfeld@sommerfeld.dev> | 2026-05-29 11:18:14 +0100 |
|---|---|---|
| committer | sommerfeld <sommerfeld@sommerfeld.dev> | 2026-05-29 11:18:14 +0100 |
| commit | ad8e14860fa0ca978f5ef6e02860d24f5e39c361 (patch) | |
| tree | c457d24ba05d5eabf149652863391df6f7c94258 /pyrightconfig.json | |
| parent | be5f8a2e6be3af4963399bb7f994f76d76b3a239 (diff) | |
| download | dotfiles-ad8e14860fa0ca978f5ef6e02860d24f5e39c361.tar.gz dotfiles-ad8e14860fa0ca978f5ef6e02860d24f5e39c361.tar.bz2 dotfiles-ad8e14860fa0ca978f5ef6e02860d24f5e39c361.zip | |
fix(suspend): switch hardened to s2idle, keep console alive, archive pstore
Previous attempt (early-loading intel_lpss_pci) did not fix the wake-from-suspend
panic on linux-hardened. The journal of the failed boot ends cleanly at the
last sync with no panic, oops, or even 'PM: suspend entry' message — the kernel
dies so fast nothing is flushed, even with panic=10 + watchdog knobs.
Three changes to make progress:
* mem_sleep_default=s2idle: switch S3 'deep' (broken firmware path on Coffee
Lake ThinkPads) to s2idle / s0ix. Many Lenovo machines only suspend reliably
via s2idle; the stock linux kernel may be masking the issue elsewhere.
* no_console_suspend: keep console alive across the suspend/resume cycle so
the panic actually prints somewhere visible, instead of being eaten when
the framebuffer goes dark.
* systemd-pstore.service: archive /sys/fs/pstore/* to /var/lib/systemd/pstore/
on every boot, so the next panic (if EFI variables capture it) survives.
Drop 'quiet' from hardened cmdline so console messages are visible.
Diffstat (limited to 'pyrightconfig.json')
0 files changed, 0 insertions, 0 deletions