[GH-ISSUE #5120] deepseek-code-v2 #28990

Closed
opened 2026-04-22 07:34:46 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @tinycrops on GitHub (Jun 18, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5120

Originally assigned to: @dhiltgen on GitHub.

What is the issue?

I don't have a problem running codestral so the problem isn't with the model size, right?

ollama run deepseek-coder-v2
pulling manifest 
pulling 5ff0abeeac1d... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏ 8.9 GB                         
pulling 732caedf08d1... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏  112 B                         
pulling 4bb71764481f... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏  13 KB                         
pulling 1c8f573e830c... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏ 1.1 KB                         
pulling 19f2fb9e8bc6... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏   32 B                         
pulling c17ee51fe152... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏  568 B                         
verifying sha256 digest 
writing manifest 
removing any unused layers 
success 
Error: llama runner process has terminated: signal: aborted (core dumped) error:failed to create context with model '/usr/share/ollama/.ollama/models/blobs/sha256-5ff0abeeac1d2dbdd5455c0b49ba3b29a9ce3c1fb181b2eef2e948689d55d046'

Same issue with deepseek-v2


OS

Linux

GPU

Nvidia

CPU

Intel

Ollama version

0.1.44

Originally created by @tinycrops on GitHub (Jun 18, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5120 Originally assigned to: @dhiltgen on GitHub. ### What is the issue? I don't have a problem running codestral so the problem isn't with the model size, right? ```bash ollama run deepseek-coder-v2 pulling manifest pulling 5ff0abeeac1d... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏ 8.9 GB pulling 732caedf08d1... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏ 112 B pulling 4bb71764481f... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏ 13 KB pulling 1c8f573e830c... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏ 1.1 KB pulling 19f2fb9e8bc6... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏ 32 B pulling c17ee51fe152... 100% ▕██████████████████████████████████████████████████████████████████████████████████▏ 568 B verifying sha256 digest writing manifest removing any unused layers success Error: llama runner process has terminated: signal: aborted (core dumped) error:failed to create context with model '/usr/share/ollama/.ollama/models/blobs/sha256-5ff0abeeac1d2dbdd5455c0b49ba3b29a9ce3c1fb181b2eef2e948689d55d046' ``` Same issue with deepseek-v2 ```bash ``` ### OS Linux ### GPU Nvidia ### CPU Intel ### Ollama version 0.1.44
GiteaMirror added the bug label 2026-04-22 07:34:46 -05:00
Author
Owner

@bunnyfu commented on GitHub (Jun 18, 2024):

This should be fixed in the build of llama.cpp from 4 days ago (which Ollama has not implemented yet).

https://github.com/ggerganov/llama.cpp/issues/7652
https://github.com/ggerganov/llama.cpp/pull/7935

<!-- gh-comment-id:2176855643 --> @bunnyfu commented on GitHub (Jun 18, 2024): This should be fixed in the build of llama.cpp from 4 days ago (which Ollama has not implemented yet). https://github.com/ggerganov/llama.cpp/issues/7652 https://github.com/ggerganov/llama.cpp/pull/7935
Author
Owner

@dhiltgen commented on GitHub (Jun 18, 2024):

Can you share your server log? If the crash is OOM related, #5121 may resolve it.

The next release 0.1.45 also has a llama.cpp update so it should pick up those fixes.

<!-- gh-comment-id:2177159267 --> @dhiltgen commented on GitHub (Jun 18, 2024): Can you share your server log? If the crash is OOM related, #5121 may resolve it. The next release 0.1.45 also has a llama.cpp update so it should pick up those fixes.
Author
Owner

@Speedway1 commented on GitHub (Jun 18, 2024):

Thanks to this issue I became aware that deepseek-coder-v2 is available on Ollama. Wishing the OP well in solving the issue, sorry that we aren't able to help.

<!-- gh-comment-id:2177211668 --> @Speedway1 commented on GitHub (Jun 18, 2024): Thanks to this issue I became aware that deepseek-coder-v2 is available on Ollama. Wishing the OP well in solving the issue, sorry that we aren't able to help.
Author
Owner

@fatualux commented on GitHub (Jun 23, 2024):

Hi,
I have found an issue with deepseek-coder-v2.
I successfully pulled the model, but cannot run it.

SYSTEM INFORMATION:
Linux
6.9.5-arch1-1 x86_64

UPTIME:
0 days, 0 hours, 2 minutes, 35 seconds

[fz@fzpc ~]$ ollama run deepseek-coder-v2
Error: Post "http://127.0.0.1:11434/api/chat": EOF

Here is what I have got in the shell where I ran ollama serve

 Device 0: NVIDIA GeForce RTX 2060, compute capability 7.5, VMM: yes
SIGSEGV: segmentation violation
PC=0x7ede02f7e1dd m=4 sigcode=1
signal arrived during cgo execution

[...]

rax    0x0
rbx    0x7eddbabff490
rcx    0x67
rdx    0x0
rdi    0x0
rsi    0x0
rbp    0x7eddbabff2e0
rsp    0x7eddbabff2b8
r8     0x7edda80008e0
r9     0x7
r10    0x7edca50ea590
r11    0xaa086e978dc30d79
r12    0x7edd9b528ca8
r13    0x0
r14    0x7edda8202388
r15    0x0
rip    0x7ede02f7e1dd
rflags 0x10283
cs     0x33
fs     0x0
gs     0x0

Any suggestions?
Thanks in advance

<!-- gh-comment-id:2185334874 --> @fatualux commented on GitHub (Jun 23, 2024): Hi, I have found an issue with deepseek-coder-v2. I successfully pulled the model, but cannot run it. ``` SYSTEM INFORMATION: Linux 6.9.5-arch1-1 x86_64 UPTIME: 0 days, 0 hours, 2 minutes, 35 seconds [fz@fzpc ~]$ ollama run deepseek-coder-v2 Error: Post "http://127.0.0.1:11434/api/chat": EOF ``` Here is what I have got in the shell where I ran ```ollama serve``` ``` Device 0: NVIDIA GeForce RTX 2060, compute capability 7.5, VMM: yes SIGSEGV: segmentation violation PC=0x7ede02f7e1dd m=4 sigcode=1 signal arrived during cgo execution [...] rax 0x0 rbx 0x7eddbabff490 rcx 0x67 rdx 0x0 rdi 0x0 rsi 0x0 rbp 0x7eddbabff2e0 rsp 0x7eddbabff2b8 r8 0x7edda80008e0 r9 0x7 r10 0x7edca50ea590 r11 0xaa086e978dc30d79 r12 0x7edd9b528ca8 r13 0x0 r14 0x7edda8202388 r15 0x0 rip 0x7ede02f7e1dd rflags 0x10283 cs 0x33 fs 0x0 gs 0x0 ``` Any suggestions? Thanks in advance
Author
Owner

@M3tu20222 commented on GitHub (Jun 24, 2024):

i am using llama3 llava or else models, but deep seek code v2 is too smal, it couldnt answer about 2 mins, other models are working. why is this so slow

<!-- gh-comment-id:2187469574 --> @M3tu20222 commented on GitHub (Jun 24, 2024): i am using llama3 llava or else models, but deep seek code v2 is too smal, it couldnt answer about 2 mins, other models are working. why is this so slow
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#28990