github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-22 13:42:25 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #10947] ollama + Llama4 image-to-text error #7208

New Issue
Closed
opened 2026-04-12 19:12:14 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 19:12:14 -05:00
Owner
Copy Link

Originally created by @stevenTzai on GitHub (Jun 2, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10947

What is the issue?

Hi~
My env:

  1. OS: ubuntu 22.04
  2. APP: ollama 0.9.0
  3. Model: Llama 4
  4. GPU: Nvidia V100

issue: ollama + Llama4 image-to-text error
I try ollama version and result below:

ollama model text-to-text image-to-text

0.6.8 Llama4 OK FAIL
0.7.0-rc1 Llama4 OK OK
0.7.0 Llama4 OK FAIL
0.8.0 Llama4 OK FAIL
0.9.0 Llama4 OK FAIL

version: 0.7.0-rc1 is work fine, but other ollama version ,the Llama4 image-to-text failed.

Anyone have the same issue?

or just nvidia v100 not support ?

Relevant log output

time=2025-06-02T13:41:13.471+08:00 level=DEBUG source=sched.go:503 msg="context for request finished"
time=2025-06-02T13:41:13.471+08:00 level=DEBUG source=sched.go:343 msg="runner with non-zero duration has gone idle, adding timer" runner.name=registry.ollama.ai/library/llama4:latest runner.inference=cuda runner.devices=3 runner.size="85.3 GiB" runner.vram="85.3 GiB" runner.parallel=15 runner.pid=49 runner.model=/root/.ollama/models/blobs/sha256-9d507a36062c2845dd3bb3e93364e9abc1607118acd8650727a700f72fb126e5 runner.num_ctx=61440 duration=2562047h47m16.854775807s
time=2025-06-02T13:41:13.471+08:00 level=DEBUG source=sched.go:361 msg="after processing request finished event" runner.name=registry.ollama.ai/library/llama4:latest runner.inference=cuda runner.devices=3 runner.size="85.3 GiB" runner.vram="85.3 GiB" runner.parallel=15 runner.pid=49 runner.model=/root/.ollama/models/blobs/sha256-9d507a36062c2845dd3bb3e93364e9abc1607118acd8650727a700f72fb126e5 runner.num_ctx=61440 refCount=0
time=2025-06-02T13:41:13.689+08:00 level=ERROR source=server.go:457 msg="llama runner terminated" error="exit status 2"

OS

Docker

GPU

Nvidia

CPU

Intel

Ollama version

0.9.0

Originally created by @stevenTzai on GitHub (Jun 2, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10947 ### What is the issue? Hi~ My env: 1. OS: ubuntu 22.04 2. APP: ollama 0.9.0 3. Model: Llama 4 4. GPU: Nvidia V100 issue: ollama + Llama4 image-to-text error I try ollama version and result below: ollama model text-to-text image-to-text ----------------------------------------------------------- 0.6.8 Llama4 OK FAIL 0.7.0-rc1 Llama4 OK OK 0.7.0 Llama4 OK FAIL 0.8.0 Llama4 OK FAIL 0.9.0 Llama4 OK FAIL version: 0.7.0-rc1 is work fine, but other ollama version ,the Llama4 image-to-text failed. Anyone have the same issue? or just nvidia v100 not support ? ### Relevant log output ```shell time=2025-06-02T13:41:13.471+08:00 level=DEBUG source=sched.go:503 msg="context for request finished" time=2025-06-02T13:41:13.471+08:00 level=DEBUG source=sched.go:343 msg="runner with non-zero duration has gone idle, adding timer" runner.name=registry.ollama.ai/library/llama4:latest runner.inference=cuda runner.devices=3 runner.size="85.3 GiB" runner.vram="85.3 GiB" runner.parallel=15 runner.pid=49 runner.model=/root/.ollama/models/blobs/sha256-9d507a36062c2845dd3bb3e93364e9abc1607118acd8650727a700f72fb126e5 runner.num_ctx=61440 duration=2562047h47m16.854775807s time=2025-06-02T13:41:13.471+08:00 level=DEBUG source=sched.go:361 msg="after processing request finished event" runner.name=registry.ollama.ai/library/llama4:latest runner.inference=cuda runner.devices=3 runner.size="85.3 GiB" runner.vram="85.3 GiB" runner.parallel=15 runner.pid=49 runner.model=/root/.ollama/models/blobs/sha256-9d507a36062c2845dd3bb3e93364e9abc1607118acd8650727a700f72fb126e5 runner.num_ctx=61440 refCount=0 time=2025-06-02T13:41:13.689+08:00 level=ERROR source=server.go:457 msg="llama runner terminated" error="exit status 2" ``` ### OS Docker ### GPU Nvidia ### CPU Intel ### Ollama version 0.9.0
GiteaMirror added the bug label 2026-04-12 19:12:14 -05:00
GiteaMirror commented 2026-04-12 19:12:16 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Jun 2, 2025):

Server logs will aid in debugging, but the most likely cause is out-of-memory (OOM). See here for mitigations.

<!-- gh-comment-id:2929361720 --> @rick-github commented on GitHub (Jun 2, 2025): [Server logs](https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues) will aid in debugging, but the most likely cause is out-of-memory (OOM). See [here](https://github.com/ollama/ollama/issues/8597#issuecomment-2614533288) for mitigations.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#7208
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?