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

[GH-ISSUE #7638] I built from source a while back and everything worked ok, the current code is dumping core, bus error. #66930

New Issue
Closed
opened 2026-05-04 08:52:46 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-05-04 08:52:46 -05:00
Owner
Copy Link

Originally created by @phalexo on GitHub (Nov 13, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/7638

Originally assigned to: @dhiltgen on GitHub.

What is the issue?

I used to build it with
go generate ./...
go build .

Is it different now? Does it detect automatically CUDA at /usr/local/cuda?

OS

Linux, Docker

GPU

Nvidia

CPU

Intel

Ollama version

cloned github latest

Originally created by @phalexo on GitHub (Nov 13, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/7638 Originally assigned to: @dhiltgen on GitHub. ### What is the issue? I used to build it with go generate ./... go build . Is it different now? Does it detect automatically CUDA at /usr/local/cuda? ### OS Linux, Docker ### GPU Nvidia ### CPU Intel ### Ollama version cloned github latest
GiteaMirror added the buildbugneeds more info labels 2026-05-04 08:52:46 -05:00
GiteaMirror commented 2026-05-04 08:52:50 -05:00
Author
Owner
Copy Link

@agreppin commented on GitHub (Nov 13, 2024):

idem here with ROCm on Ubuntu 24.04, v0.4.1 log attached, same result with commit 65973ceb

ollama-v0.4.1-rocm-v6.2.4.log

PS: please can you provide some tips on how to debug the server/runner in the developers docs

<!-- gh-comment-id:2472053740 --> @agreppin commented on GitHub (Nov 13, 2024): idem here with ROCm on Ubuntu 24.04, v0.4.1 log attached, same result with commit 65973ceb [ollama-v0.4.1-rocm-v6.2.4.log](https://github.com/user-attachments/files/17724535/ollama-v0.4.1-rocm-v6.2.4.log) PS: please can you provide some tips on how to debug the server/runner in the developers docs
GiteaMirror commented 2026-05-04 08:52:53 -05:00
Author
Owner
Copy Link

@phalexo commented on GitHub (Nov 13, 2024):

idem here with ROCm on Ubuntu 24.04, v0.4.1 log attached, same result with commit 65973ce

ollama-v0.4.1-rocm-v6.2.4.log

PS: please can you provide some tips on how to debug the server/runner in the developers docs

I cannot be sure what your problem, but I think I figured what mine is. Ollama people decided to get "clever" how they identify a CUDA installation, and they just ignore variables like CUDA_ROOT, CUDA_HOME and instead look at symbolic links like /usr/local/cuda-11, which was the OLDER version. From that point different things did not match.

<!-- gh-comment-id:2472215353 --> @phalexo commented on GitHub (Nov 13, 2024): > idem here with ROCm on Ubuntu 24.04, v0.4.1 log attached, same result with commit [65973ce](https://github.com/ollama/ollama/commit/65973ceb6417c2e2796fa59bd3225bc7bd79b403) > > [ollama-v0.4.1-rocm-v6.2.4.log](https://github.com/user-attachments/files/17724535/ollama-v0.4.1-rocm-v6.2.4.log) > > PS: please can you provide some tips on how to debug the server/runner in the developers docs I cannot be sure what your problem, but I think I figured what mine is. Ollama people decided to get "clever" how they identify a CUDA installation, and they just ignore variables like CUDA_ROOT, CUDA_HOME and instead look at symbolic links like /usr/local/cuda-11, which was the OLDER version. From that point different things did not match.
GiteaMirror commented 2026-05-04 08:52:56 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Nov 13, 2024):

We're working to improve the new build in PR #7499

<!-- gh-comment-id:2474449115 --> @dhiltgen commented on GitHub (Nov 13, 2024): We're working to improve the new build in PR #7499
GiteaMirror commented 2026-05-04 08:52:57 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Nov 13, 2024):

@phalexo please give the change above a try and let us know if it clears up your build glitch, or if there's still more work to do.

The docs/development.md has been updated in that PR to provide additional guidance on building.

<!-- gh-comment-id:2474611352 --> @dhiltgen commented on GitHub (Nov 13, 2024): @phalexo please give the change above a try and let us know if it clears up your build glitch, or if there's still more work to do. The docs/development.md has been updated in that PR to provide additional guidance on building.
GiteaMirror commented 2026-05-04 08:52:58 -05:00
Author
Owner
Copy Link

@phalexo commented on GitHub (Nov 13, 2024):

I addressed the core dump problem by deleting old CUDA distribution. The
second problem that caused the runner to die, I had to drop the version
to V0.3.11. So at least you know that v0.3.11 works with
Qwen2.5-32b-instruct-Q8_0

On Wed, Nov 13, 2024 at 2:48 PM Daniel Hiltgen @.***>
wrote:

@phalexo https://github.com/phalexo please give the change above a try
and let us know if it clears up your build glitch, or if there's still more
work to do.

The docs/development.md has been updated in that PR to provide additional
guidance on building.

—
Reply to this email directly, view it on GitHub
https://github.com/ollama/ollama/issues/7638#issuecomment-2474611352,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDD3ZIIJDJLJYOB2GUZNZ32AOUIFAVCNFSM6AAAAABRVHSHSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZUGYYTCMZVGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

<!-- gh-comment-id:2474934565 --> @phalexo commented on GitHub (Nov 13, 2024): I addressed the core dump problem by deleting old CUDA distribution. The second problem that caused the runner to die, I had to drop the version to V0.3.11. So at least you know that v0.3.11 works with Qwen2.5-32b-instruct-Q8_0 On Wed, Nov 13, 2024 at 2:48 PM Daniel Hiltgen ***@***.***> wrote: > @phalexo <https://github.com/phalexo> please give the change above a try > and let us know if it clears up your build glitch, or if there's still more > work to do. > > The docs/development.md has been updated in that PR to provide additional > guidance on building. > > — > Reply to this email directly, view it on GitHub > <https://github.com/ollama/ollama/issues/7638#issuecomment-2474611352>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABDD3ZIIJDJLJYOB2GUZNZ32AOUIFAVCNFSM6AAAAABRVHSHSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZUGYYTCMZVGI> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
GiteaMirror commented 2026-05-04 08:52:59 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Dec 10, 2024):

@phalexo PR #7499 is now merged. Please give the new build a try and if it resolves your problem, go ahead and close the issue. If not, please share updated details so I can take another look.

<!-- gh-comment-id:2532713713 --> @dhiltgen commented on GitHub (Dec 10, 2024): @phalexo PR #7499 is now merged. Please give the new build a try and if it resolves your problem, go ahead and close the issue. If not, please share updated details so I can take another look.
GiteaMirror commented 2026-05-04 08:53:00 -05:00
Author
Owner
Copy Link

@phalexo commented on GitHub (Dec 10, 2024):

Go ahead and close it, as I don't quite remember the details now.

On Tue, Dec 10, 2024, 2:45 PM Daniel Hiltgen @.***>
wrote:

@phalexo https://github.com/phalexo PR #7499
https://github.com/ollama/ollama/pull/7499 is now merged. Please give
the new build a try and if it resolves your problem, go ahead and close the
issue. If not, please share updated details so I can take another look.

—
Reply to this email directly, view it on GitHub
https://github.com/ollama/ollama/issues/7638#issuecomment-2532713713,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDD3ZK3TO6ID4E2KZVNSJD2E5AD3AVCNFSM6AAAAABRVHSHSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZSG4YTGNZRGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

<!-- gh-comment-id:2532721426 --> @phalexo commented on GitHub (Dec 10, 2024): Go ahead and close it, as I don't quite remember the details now. On Tue, Dec 10, 2024, 2:45 PM Daniel Hiltgen ***@***.***> wrote: > @phalexo <https://github.com/phalexo> PR #7499 > <https://github.com/ollama/ollama/pull/7499> is now merged. Please give > the new build a try and if it resolves your problem, go ahead and close the > issue. If not, please share updated details so I can take another look. > > — > Reply to this email directly, view it on GitHub > <https://github.com/ollama/ollama/issues/7638#issuecomment-2532713713>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABDD3ZK3TO6ID4E2KZVNSJD2E5AD3AVCNFSM6AAAAABRVHSHSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZSG4YTGNZRGM> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
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 build 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#66930
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?