Troubleshooting guides

Preserve evidence before changing the system

A useful troubleshooting record identifies the task, the resource boundary, the time of the symptom, and the evidence that was collected. Start with read-only checks where possible. Then test a specific explanation with one reversible change, retaining both successful and unsuccessful results.

This collection covers different failure points: Linux swap-file activation, CUDA allocations, cloud group limits, and an unresponsive laptop session. The common method is to locate the failing layer before applying a remedy. More host swap is not an automatic answer to a GPU allocation error, and spare host capacity is not proof that a constrained container may use it.

Use Mem Swap fundamentals when terminology is the obstacle. Move to the Linux, AI, cloud, or laptop overview to choose the relevant observations.

Preserve the original configuration and a recovery path before disruptive work. Avoid several simultaneous tweaks that make the result impossible to explain. A narrow diagnosis with a reproducible fix is more valuable than an impressive command sequence whose effect is uncertain.