You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Engine] Inkling-2-Mini SQ-10 segfaults in CPU expert computation on RTX 4070 SUPER #6569
Inkling-2-Mini SQ-10 loaded and completed the one-token startup check. On a 7,424-token request within the configured 8,192-token context, the engine exited with -11 (SIGSEGV) before generating a reply. The expected result is that the engine processes the prompt and returns a reply.
A standalone benchmark reproduced the segfault with a synthetic 128-token prompt, FP16 KV, and drafting disabled. It exited with status 139 before producing a result.
Smallest steps or command that reproduce it
With SQ-10 already installed, run the packaged engine directly:
Terminal 0.2.19, strata-inkling 0.1.65, Linux x86_64 CUDA 13 package, engine commit c6f6427d9de9.
Graphics card, memory and system
One NVIDIA GeForce RTX 4070 SUPER (12,282 MiB reported), driver 615.78.08, AMD Ryzen 7 7800X3D, 61 GiB usable RAM, Omarchy 4.5.0, Linux 7.2.15-1-omarchy x86_64.
Model, size and settings
Inkling-2-Mini SQ-10, 8K context, one request, vision off. The original serving run used FP8 KV, DSpark, a 2,048 MiB VRAM reserve, and Strata-generated expert budgets of 8.60 GB VRAM and 0.00 GB RAM. The engine reported 2,339 experts in VRAM and 733 on the host.
The kernel logged segfault at 900 in strata-inkling. No OOM kill appeared in the kernel journal around the serving crash. strata doctor --live --profile launch-inkling-sq10-8k found the engine, model and tokenizer files and reported Live GPU probe: ok.
Additional reproduction and serving timeline from the same machine and engine build.
FP8 benchmark reproduction
The engine also exited with status 139 on a synthetic 512-token prompt with FP8 KV, drafting disabled, and an explicit 3 GB RAM expert budget. The FP16 reproduction in the issue body used a separate benchmark run.
The one-token startup check completed. The next request produced these server log entries.
[strata] reading the prompt: 7,424 tokens, 10 s so far
[strata] reading the prompt: 7,424 tokens, 20 s so far
[strata] reading the prompt: 7,424 tokens, 30 s so far
[strata] the engine stopped unexpectedly (exit code -11).
[strata] done: 0 tokens in 39 s (no speed) (error, cancel=False)
The engine-stop line is shortened. The backtrace in the issue body is from this serving crash.
Activity
mskutin commentedon Nov 22, 2026
Additional reproduction and serving timeline from the same machine and engine build.
FP8 benchmark reproduction
The engine also exited with status
139on a synthetic 512-token prompt with FP8 KV, drafting disabled, and an explicit 3 GB RAM expert budget. The FP16 reproduction in the issue body used a separate benchmark run.Original serving timeline
The one-token startup check completed. The next request produced these server log entries.
The engine-stop line is shortened. The backtrace in the issue body is from this serving crash.