From a8f7e9b9c089577b299afc04bd1e1be040197995 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Thu, 9 Jul 2026 14:02:20 -0500 Subject: docs: remove personal paths and false co-authorship before release The repo carries an open task to publish it, and docs/ leaked things a clone could neither use nor should see. Absolute paths under one user's home become the repo root, a home-relative path, or a named variable, so the snippets stay runnable for anyone. The testinfra example takes its user from an env var instead of hardcoding one. References into a private sibling project and into the gitignored tooling directory are replaced by what they mean; as written they were dead links in any clone but the author's. Five documents claimed a co-author who is not a person. An #+AUTHOR line survives conversion into docx, a wiki page, or a PDF, so it is worth being exact about: these documents have one author. --- docs/workflows/strix-soak-watch.org | 10 ++++------ docs/workflows/system-health-check.org | 4 ++-- 2 files changed, 6 insertions(+), 8 deletions(-) (limited to 'docs/workflows') diff --git a/docs/workflows/strix-soak-watch.org b/docs/workflows/strix-soak-watch.org index e2fbf68..b86921d 100644 --- a/docs/workflows/strix-soak-watch.org +++ b/docs/workflows/strix-soak-watch.org @@ -1,5 +1,5 @@ #+TITLE: Strix Halo SMU Deadlock — Kernel Update Watch -#+AUTHOR: Craig Jennings & Claude +#+AUTHOR: Craig Jennings #+DATE: 2026-05-10 * Purpose @@ -13,7 +13,7 @@ This is a one-time hardware/kernel issue. Delete this file when the strix kernel - *Boot kernel:* =linux-lts-strix 6.18.25-1= (custom AUR-style local build), GRUB default pinned - *SMC firmware:* =100.6.0= (from =/sys/kernel/debug/dri/*/amdgpu_firmware_info= SMC line) - *Cmdline workaround:* =amdgpu.no_vpe_idle_pg=1= active -- *Soak verdict:* HOLDING since 2026-04-30 — zero SMU/dcn35/VPE freeze signature hits (see =~/projects/home/assets/archive/2026-05-04-strix-soak-check-holding.org= (stays in the home project)) +- *Soak verdict:* HOLDING since 2026-04-30 — zero SMU/dcn35/VPE freeze signature hits (see the 2026-05-04 soak-check verdict, archived outside this repo) * Background (one-paragraph summary so future sessions don't have to reconstruct it) @@ -131,10 +131,8 @@ Drop the matching patches from the PKGBUILD on next strix rebuild; keep 0004 unt * Reference Artifacts -- Soak verdict (archived): =~/projects/home/assets/archive/2026-05-04-strix-soak-check-holding.org= (stays in the home project) -- VPE-patch deployment session: =.ai/sessions/2026-04-29-23-35-linux-lts-strix-vpe-patch-deployed.org= -- Soak fix + housekeeping session: =.ai/sessions/2026-05-03-06-48-soak-fix-and-velox-sync-housekeeping.org= -- Verdict-holds session: =.ai/sessions/2026-05-05-01-48-strix-verdict-holds-mybitch-soak-deferred.org= +- Soak verdict (archived): the 2026-05-04 soak-check verdict, archived outside this repo +- Working records for the VPE-patch deployment (2026-04-29), the soak fix (2026-05-03), and the verdict-holds check (2026-05-05) are archived outside this repo. - Forum thread: https://community.frame.work/t/smu-deadlock-system-freeze-on-fedora-43/81795 - Build dir: =~/build/linux-lts-patched/linux-lts/= - Inventory: the =ratio - Desktop Workstation= node in =~/org/roam/hardware/= (resolve by =#+HOSTNAME: ratio=) diff --git a/docs/workflows/system-health-check.org b/docs/workflows/system-health-check.org index 98fa17f..b4f34a5 100644 --- a/docs/workflows/system-health-check.org +++ b/docs/workflows/system-health-check.org @@ -1,5 +1,5 @@ #+TITLE: System Health Check Workflow -#+AUTHOR: Craig Jennings & Claude +#+AUTHOR: Craig Jennings #+DATE: 2026-02-27 * Overview @@ -1030,7 +1030,7 @@ Each entry is scoped to one host (or =any=). When Phase 1 cross-references findi ** 2026-06-13: ratio — dockerized telega-server SIGSEGVs in musl build :host: ratio -- Symptom: =coredumpctl= shows repeated SIGSEGVs from =telega-server -O 31 -l /home/cjennings/.telega/telega-server.log -v 3= running inside the Telega Docker container. Example stack is entirely in the container's musl loader plus =/usr/bin/telega-server=, not host kernel, GPU, storage, or memory paths. +- Symptom: =coredumpctl= shows repeated SIGSEGVs from =telega-server -O 31 -l ~/.telega/telega-server.log -v 3= running inside the Telega Docker container. Example stack is entirely in the container's musl loader plus =/usr/bin/telega-server=, not host kernel, GPU, storage, or memory paths. - Evidence: =~/.telega/telega-server.log= ends with =Unexpected char 'm' in plist value= followed by =Assertion failed: false (telega-dat.c: tdat_plist_value: 500)=. Surrounding TDLib traffic includes sticker/custom-emoji metadata such as =documentAttributeCustomEmoji= and =PhotoSizeSourceThumbnail[Thumbnail, type = m]=. - Prior local triage: =~/.emacs.d/todo.org= recorded the same issue on 2026-06-11 as spontaneous memory-corruption crashes in =zevlg/telega-server:latest='s musl build, with several coredumps occurring without action-verb traffic. Telega package installed at the 2026-06-13 health check was =20260513.509=; MELPA had =20260604.2321= available. - Functional status at 2026-06-13 check: no coredumps yet that day; Telegram scans still worked from cached chat state. Treat as an app/server-container crash, not a machine-health fault. -- cgit v1.2.3