github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #15396] Update 0.20.3 required machine restart? new requirement? #9846

New Issue
Closed
opened 2026-04-12 22:42:40 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 22:42:40 -05:00
Owner
Copy Link

Originally created by @SingKS8 on GitHub (Apr 7, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15396

What is the issue?

I am run 0.20.3 in LXC on PVE vgpu with 4X3090.

Before I restarted the whole machine, no matter which method to run model, the model only run on CPU.
The mimutes before updated to 0.20.3, the 0.20.2 worked well.

Is it new requirement for update, restarting machine?

If it is yes, I will add a rule in my notes.
If it is not, I hope below before / after log could help to find some clues.

before.log

after.log

Relevant log output

OS

Linux

GPU

Nvidia

CPU

AMD

Ollama version

0.20.3

Originally created by @SingKS8 on GitHub (Apr 7, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15396 ### What is the issue? I am run 0.20.3 in LXC on PVE vgpu with 4X3090. Before I restarted the whole machine, no matter which method to run model, the model only run on CPU. The mimutes before updated to 0.20.3, the 0.20.2 worked well. ### Is it new requirement for update, restarting machine? If it is yes, I will add a rule in my notes. If it is not, I hope below before / after log could help to find some clues. [before.log](https://github.com/user-attachments/files/26544167/before.log) [after.log](https://github.com/user-attachments/files/26544171/after.log) ### Relevant log output ```shell ``` ### OS Linux ### GPU Nvidia ### CPU AMD ### Ollama version 0.20.3
GiteaMirror added the bug label 2026-04-12 22:42:40 -05:00
GiteaMirror commented 2026-04-12 22:42:41 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 7, 2026):

Updating does not require a machine restart. Unfortunately the log level in before.log wasn't high enough to record the reason for the GPU detection failure.

<!-- gh-comment-id:4200989220 --> @rick-github commented on GitHub (Apr 7, 2026): Updating does not require a machine restart. Unfortunately the log level in `before.log` wasn't high enough to record the reason for the GPU detection failure.
GiteaMirror commented 2026-04-12 22:42:41 -05:00
Author
Owner
Copy Link

@SingKS8 commented on GitHub (Apr 9, 2026):

I cannot reproduce on 0.20.3, and 0.20.4 is good after installed.
I close this issue.

<!-- gh-comment-id:4214453647 --> @SingKS8 commented on GitHub (Apr 9, 2026): I cannot reproduce on 0.20.3, and 0.20.4 is good after installed. I close this issue.
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#9846
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?