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

[GH-ISSUE #8985] Model switching bug #31593

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

Originally created by @abnormalboy on GitHub (Feb 10, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/8985

What is the issue?

When I switch the model from deepseek-r1:32b-qwen-distill-q8_0 to deepseek-r1:32b, the gpu can't load it, and the video memory only takes up 414M. The api call will keep getting stuck. Is it a potential bug or what may be the cause?

Relevant log output

When the video memory is deepseek-r1:32b-qwen-distill- q8_0, the video memory occupies:

Image

After I switched the model to deepseek-r1:32b, the video memory usage:

Image

OS

Linux

GPU

Nvidia

CPU

Other

Ollama version

0.5.7

Originally created by @abnormalboy on GitHub (Feb 10, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/8985 ### What is the issue? When I switch the model from deepseek-r1:32b-qwen-distill-q8_0 to deepseek-r1:32b, the gpu can't load it, and the video memory only takes up 414M. The api call will keep getting stuck. Is it a potential bug or what may be the cause? ### Relevant log output When the video memory is deepseek-r1:32b-qwen-distill- q8_0, the video memory occupies: <img width="319" alt="Image" src="https://github.com/user-attachments/assets/4f7c85ce-3709-4846-981f-a7810699244b" /> After I switched the model to deepseek-r1:32b, the video memory usage: <img width="318" alt="Image" src="https://github.com/user-attachments/assets/67a68841-8566-441b-a7ca-c75825699301" /> ### OS Linux ### GPU Nvidia ### CPU Other ### Ollama version 0.5.7
GiteaMirror added the bugneeds more info labels 2026-04-22 12:12:10 -05:00
GiteaMirror commented 2026-04-22 12:12:13 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Feb 10, 2025):

Server logs may aid in debugging.

<!-- gh-comment-id:2647455595 --> @rick-github commented on GitHub (Feb 10, 2025): [Server logs](https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues) may aid in debugging.
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 needs more info
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#31593
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?