ollama - 💡(How to fix) Fix Gemma 4 (26b, 31b) crashes with segfault on DGX Spark (ARM64 + Blackwell GB10) [4 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
ollama/ollama#15318Fetched 2026-04-08 02:44:15
View on GitHub
Comments
4
Participants
3
Timeline
7
Reactions
0
Author
Timeline (top)
commented ×4subscribed ×3

Error Message

Error from logs: model failed to load, this may be due to resource limitations or an internal error

RAW_BUFFERClick to expand / collapse

Ollama version: 0.20.0 OS: Ubuntu ARM64 (DGX Spark) GPU: NVIDIA Blackwell GB10 (128 GB unified memory)

What happened: Both gemma4:26b and gemma4:31b crash with segfault when loading. No other models are loaded, 118 GB RAM available.

Error from logs: llama runner terminated: exit status 2 model failed to load, this may be due to resource limitations or an internal error Full register dump visible in journalctl -u ollama.

Other models work fine on same hardware: Nemotron 3 Super 120B, Qwen 3.5 35B, Qwen 2.5 72B — all load and run without issues.

Gemma 4 26b works on MacBook Pro M3 Max (128 GB) with LM Studio / MLX.

extent analysis

TL;DR

The issue may be resolved by investigating resource limitations or internal errors specific to the Gemma 4 models on the Ubuntu ARM64 environment.

Guidance

  • Verify the system's resource utilization when loading the Gemma 4 models to identify potential bottlenecks.
  • Compare the loading process of the working models (Nemotron 3 Super 120B, Qwen 3.5 35B, Qwen 2.5 72B) with the Gemma 4 models to identify any differences in resource allocation or handling.
  • Check the journalctl logs for the full register dump to gain more insights into the cause of the segfault.
  • Consider testing the Gemma 4 models on a different environment, like the MacBook Pro M3 Max, to see if the issue is specific to the Ubuntu ARM64 setup.

Notes

The issue seems to be specific to the Gemma 4 models on the Ubuntu ARM64 environment, and more investigation is needed to determine the root cause.

Recommendation

Apply workaround: Try to allocate more resources or adjust the loading process for the Gemma 4 models to see if it resolves the issue, as the models work fine on a different hardware setup.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

ollama - 💡(How to fix) Fix Gemma 4 (26b, 31b) crashes with segfault on DGX Spark (ARM64 + Blackwell GB10) [4 comments, 3 participants]