Gotcha Checks

torch.version.cuda is the authoritative signal: it should report 13.x. Don’t rely on pip show torch | grep cu130 — NGC container builds (e.g. nvcr.io/nvidia/pytorch:25.11-py3) build torch internally against CUDA 13 with no +cu130 wheel tag, so the absence of a cu130 tag in pip show output is NOT a failure by itself on those containers. The ctypes load confirms libcudart.so.13 is actually present on the system; if it raises OSError, the driver/runtime install is the problem, not the wheel. ldconfig -p lists every CUDA runtime version currently registered — a libcudart.so.12 entry alongside libcudart.so.13 is a common leftover from an earlier install and a likely ABI-mismatch source.

G2: flash-attn — Presence Check and the Unsloth Override

Don’t assume this import fails — it depends on the environment. On a bare-pip install it’s expected to fail (no aarch64/ sm_121 wheel exists), confirming no training code path silently depends on flash-attn. On an NGC PyTorch container (confirmed on nvcr.io/nvidia/pytorch:25.09-py3), flash-attn 2.7.4.post1 ships pre-bundled and a live flash_attn_func kernel call on GB10 (capability (12, 1)) executes successfully with correct output shape — the “no sm_121 kernels” framing only applies to building it yourself, not to what these containers already carry.

The actual trap on a container with flash-attn present: Unsloth’s import-time patch banner reports FA2 = True and auto-prefers flash-attn over SDPA — including when the caller explicitly requested attn_implementation="sdpa". Unsloth’s loader (unsloth/models/llama.py, 2026.7.2) calls its internal resolve_attention_implementation(...) without forwarding the caller’s attn_implementation as that function’s requested_attn_implementation parameter, then pops the kwarg outright with a # No need since we auto call it comment — silently discarding whatever was requested. Confirmed via a live load: attn_implementation="sdpa" passed explicitly still resolved to model.config._attn_implementation == "flash_attention_2".

The only working override on this Unsloth version, for any model routed through Unsloth’s llama-architecture loader (unsloth/models/llama.py — this covers more than one base model family; see finetuning-method-selection‘s model catalog for which) when flash-attn is importable, is a monkeypatch before calling from_pretrained:

This forces resolve_attention_implementation‘s auto-resolution down its elif supports_sdpa: branch instead of the flash-attn branch — confirmed working (config._attn_implementation == "sdpa" after the monkeypatch). On plain TRL/PEFT (bypassing Unsloth entirely — see lora-qlora-recipes‘ references/unsloth-trl-mapping.md escape hatch), attn_implementation="sdpa" passed to AutoModelForCausalLM.from_pretrained is honored correctly; this gap is Unsloth-specific, not a general TRL/transformers issue.

G3: UMA OOM Below 128GB

Read real memory pressure from free -g, not nvidia-smi — unified memory means CUDA allocations and host RAM share one pool, and nvidia-smi only reports the CUDA side. On some driver/setup combinations, nvidia-smi --query-gpu=memory.used, memory.total --format=csv doesn’t just undercount — it returns [N/A], [N/A] for the whole-GPU memory query outright. A script that greps for a numeric value there gets nothing, not a misleading number; don’t build a headroom check on that query on this hardware. If free -g shows most of the 128GB consumed while a load is failing, reclaim it:

This needs root and flushes the page cache system-wide — every process on the box loses cached file reads, not just the training job. Run it between runs when memory looks pinned by stale mmap’d pages, not as a routine step during training.

G4: Thermal Throttling

Sampling loop (-l 5 = every 5 seconds); let it run for at least 10–15 minutes on a representative workload before judging. Rated power is 240W; if draw plateaus around 100W while temperature keeps climbing or has already plateaued high, the box is throttling. A rising temperature with power still near peak is not yet a throttle event — keep watching. Interrupt with Ctrl-C when done; this does not need root.

G5: Bandwidth Ceiling

Intrusive, unlike the other checks in this file — do not run against an active workload. It allocates ~4GB on a UMA system where GPU and host memory share one pool, and repeatedly clones that tensor. Run only on an idle host; a box with another job already using most of its 128GB headroom can OOM that job.

Expect roughly 180–192 GB/s, not the 273 GB/s spec figure. If a throughput plan assumed the spec number, revise it against this measured range before committing to a schedule.

G6: Global UMA Resource Contention

List every GPU-resident process before starting a long run. nvidia-smi shows per-process memory; the ps filter catches inference servers (vLLM, Ollama) that may not show up clearly in nvidia-smi output on unified memory. The one-heavy-job rule applies to uncapped or near-capacity workloads — stop unrelated servers before a run that needs the full 128GB pool, or that runs alongside another process without an explicit memory cap. It does not apply to small, memory-capped coexistence: a <4GB LoRA fine-tune has been observed running cleanly alongside a vLLM server started with --gpu-memory-utilization 0.5 (or lower) on the same box — check the other process’s own memory cap, not just its presence, before deciding whether it needs to be stopped.

G7: NVFP4 Slower Than FP8 on SM121

Expect (12, 1) on GB10 — this confirms SM121. SM121 lacks a native cvt.e2m1x2 conversion path, so NVFP4 kernels not compiled for the sm_121a target fall back to a slower path, roughly 32% behind FP8. Check the kernel build’s target arch (often TORCH_CUDA_ARCH_LIST or a similar build flag) before assuming NVFP4 is the faster choice on this hardware.

G8: Stale Official Playbooks

Requires the gh CLI authenticated, or substitute a browser visit to the same URL. Scan open issues for the specific playbook and command being followed before trusting it verbatim for a long or expensive run.

G9: Container-First, Not Bare Pip

The first block checks Docker’s /.dockerenv and Podman’s /run/.containerenv marker files, then falls back to a cgroup-string check — a single grep docker /proc/1/cgroup alone is not reliable: cgroup v2 layouts and some runtimes/namespaces hide the runtime name, so a failed match is “unknown,” never proof of a bare host. The second command lists the versions actually installed — compare against the pinned set in an NGC or Unsloth image if running bare pip, to catch drift early rather than at import time.

G10: Dual-Spark Is DDP/FSDP Only

Search recursively, not just the current directory — a non-recursive *.yaml *.yml glob misses nested configs, and a redirected/suppressed error there reads as “no TP configuration” when it may just be “wrong directory.” If the workload’s config path is already known, pass it explicitly instead of searching. Any match on a two-Spark job is a configuration error — switch to DDP or FSDP before launching; TP is not viable across the ConnectX-7 link on this hardware.