Crash Recovery & Incident Reports

This section tracks system crashes, GUI freezes, and recovery procedures.

Symptoms:

• xfreerdp3 session froze in fullscreen, preventing desktop access via GUI.
• Attempted 'sudo kill' and 'pkill' from a local terminal failed to terminate PID 9423.
• Gemini CLI on the main display was glitched, looping output to the console.

Root Cause Analysis:

• RDP Hang: Likely related to iGPU VF (Virtual Function) stability. Kernel logs showed multiple “VF1 FLR” (Function Level Reset) events.
• Gemini Loop: Multiple orphaned or glitched node processes (PIDs 6431, 6454) were running in the background.
• Segfaults: dmesg reported node segfaults in `libgcc_s.so.1`.

Recovery Steps:

• Terminated the frozen xfreerdp3 process using `kill -9 9423` (SIGKILL).
• Identified and killed looping gemini/node processes using `kill -9 6431 6454`.
• Verified KWin compositor state via D-Bus (`qdbus6 org.kde.KWin /KWin`) to ensure no ghost fullscreen windows remained.

Status: Resolved. System responsiveness restored.

* Exit Code: 255 * Mode: performance * VM IP: 192.168.122.69

* Exit Code: 255 * Mode: performance * VM IP: 192.168.122.69

* Exit Code: 24 * Mode: performance * VM IP: 192.168.122.69

* Exit Code: 24 * Mode: performance * VM IP: 192.168.122.69

* Exit Code: 136 * Mode: performance * VM IP: 192.168.122.69

* Exit Code: 137 * Mode: performance * VM IP: 192.168.122.69

* Exit Code: 134 * Mode: performance * VM IP: 192.168.122.69

* Exit Code: 24 * Mode: high-perf * VM IP: 192.168.122.69

* Exit Code: 136 * Mode: high-perf * VM IP: 192.168.122.69

* Exit Code: 139 * Mode: high-perf * VM IP: 192.168.122.69

* Exit Code: 139 * Mode: high-perf * VM IP: 192.168.122.69