ollama - 💡(How to fix) Fix MLX runner failed with qwen3.6:35b-a3b-coding-bf16 format=json [2 comments, 2 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#15822Fetched 2026-04-27 05:29:05
View on GitHub
Comments
2
Participants
2
Timeline
3
Reactions
0
Timeline (top)
commented ×2labeled ×1

Error Message

{"error":"mlx runner failed: time=2026-04-26T21:12:59.383+09:00 level=INFO source=pipeline.go:129 msg="Prompt processing progress" processed=10 total=11"}

Code Example

{"error":"mlx runner failed: time=2026-04-26T21:12:59.383+09:00 level=INFO source=pipeline.go:129 msg=\"Prompt processing progress\" processed=10 total=11"}
RAW_BUFFERClick to expand / collapse

What is the issue?

curl http://localhost:11434/api/chat -d '{ "model": "qwen3.6:35b-a3b-coding-bf16",
"messages": [{"role":"user","content":"hi"}], "format": "json",
"stream": false }'

Relevant log output

{"error":"mlx runner failed: time=2026-04-26T21:12:59.383+09:00 level=INFO source=pipeline.go:129 msg=\"Prompt processing progress\" processed=10 total=11"}

OS

macOS

GPU

Apple

CPU

Apple

Ollama version

ollama version is 0.21.2

extent analysis

TL;DR

The issue with the curl request to the API endpoint may be related to the model or input data, and checking the model compatibility or input format could be the first step towards a solution.

Guidance

  • Verify that the model "qwen3.6:35b-a3b-coding-bf16" is compatible with the current version of Ollama (0.21.2) and the Apple GPU.
  • Check the input data format, specifically the "messages" field, to ensure it matches the expected format for the API endpoint.
  • Investigate the "mlx runner failed" error message in the log output, which may indicate a problem with the pipeline or model execution.
  • Consider checking the Ollama documentation for any specific requirements or restrictions on model usage or input data.

Notes

The provided log output does not contain a clear error message, and the issue may require further investigation or additional information to determine the root cause.

Recommendation

Apply workaround: Check model compatibility and input data format, as these are the most likely causes of the issue, and adjusting these may resolve the problem without requiring an upgrade or significant changes.

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 MLX runner failed with qwen3.6:35b-a3b-coding-bf16 format=json [2 comments, 2 participants]