mirror of
https://github.com/kuhyx/testsAndMisc.git
synced 2026-11-10 22:27:01 +01:00
Krzysztof kuhy Rudnicki
b7523d1691
Investigated whether this session caused the 11:33 hard freeze. It did not, and the evidence is recorded in the evidence artifact: - No OOM kill, no oom_reaper, no hung-task or soft-lockup message, and no kernel message AT ALL after 11:20. The log stops mid-line at 11:33:15 -- a hard hang, not a process the kernel was fighting. - Last commit 11:30:32; last jail trace 11:11:57, 21 minutes earlier. The session was idle when the machine died. - Steam wrote a crash minidump at 11:31:10 and at-spi2 disabled an unresponsive app at 11:32:06, on an RTX 3090. Correlation only -- a hard hang leaves no log to prove cause. - Nothing survived the reboot: no stray unshare/kcov, no leftover tmpdirs, no leaked mounts, and the live /etc and /usr/local/bin files keep their original dates. Hardened anyway, because the jail had one genuinely unbounded behaviour: a case could run forever. Two hangs yesterday came from a `crontab -` fallback inheriting the caller's stdin. Each case now runs under `timeout --kill-after=10s` (default 120s, --timeout to override) with stdin from /dev/null, and a timed-out case WARNS by name instead of being swallowed -- a silent timeout looks identical to an unreachable line in the report. Verified: a `sleep 600` subject now ends in 5s with --timeout 5s. dot_resolver_install.sh still measures 39/39 = 100.00%. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DbD4nco3EgL1UFoZKmKsLE |
||
|---|---|---|
| .. | ||
| explanations | ||
| superpowers | ||
| agent-harness-evaluation-2026-08-18.md | ||
| app-split-recipes.md | ||
| device-owner-wipe-checklist.md | ||
| dns-filtering-parked.md | ||
| mcp-shortlist.html | ||
| python-split-recipes.md | ||
| shared-checkout-safety.md | ||
| shell-split-harness.md | ||
| shell-split-recipes.md | ||
| shell-split-verification.md | ||
| syncyomi-restore-runbook.md | ||