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

[PR #5128] [MERGED] Fix levelzero empty symbol detect #42941

New Issue
Closed
opened 2026-04-24 22:39:02 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-24 22:39:02 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/5128
Author: @zhewang1-intc
Created: 6/19/2024
Status: ✅ Merged
Merged: 6/19/2024
Merged by: @dhiltgen

Base: main ← Head: fix_levelzero_empty_symbol_detect

📝 Commits (2)

  • 755b4e4 Revert "gpu: add env var for detecting Intel oneapi gpus (#5076)"
  • badf975 get real func ptr.

📊 Changes

3 files changed (+27 additions, -36 deletions)

View changed files

📝 envconfig/config.go (+0 -7)
📝 gpu/gpu.go (+26 -28)
📝 gpu/gpu_info_oneapi.c (+1 -1)

📄 Description

we notice many users report ollama crash on Windows platform when ollama try to discover Intel GPUs after introducing Intel GPUs support.
this issue may occur on some older Intel CPUs which before 11Gen.
this is due to the driver library of iGPUs before 11Gen processors don't have the symbols which initial level-zero needed, like zesInit , and there is also a bug in oneapi_init, l[i].p is a pointer to pointer, func ptr stored in *l[i].p so we should detect whether *l[i].p is null ptr to check whether we load the func successfully.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/5128 **Author:** [@zhewang1-intc](https://github.com/zhewang1-intc) **Created:** 6/19/2024 **Status:** ✅ Merged **Merged:** 6/19/2024 **Merged by:** [@dhiltgen](https://github.com/dhiltgen) **Base:** `main` ← **Head:** `fix_levelzero_empty_symbol_detect` --- ### 📝 Commits (2) - [`755b4e4`](https://github.com/ollama/ollama/commit/755b4e4fc291366595ed7bfb37c2a91ff5834df8) Revert "gpu: add env var for detecting Intel oneapi gpus (#5076)" - [`badf975`](https://github.com/ollama/ollama/commit/badf975e45005c45cf5d7794a18c88f4e069f89c) get real func ptr. ### 📊 Changes **3 files changed** (+27 additions, -36 deletions) <details> <summary>View changed files</summary> 📝 `envconfig/config.go` (+0 -7) 📝 `gpu/gpu.go` (+26 -28) 📝 `gpu/gpu_info_oneapi.c` (+1 -1) </details> ### 📄 Description we notice many users report ollama crash on Windows platform when ollama try to discover Intel GPUs after introducing Intel GPUs support. this issue may occur on some older Intel CPUs which before 11Gen. this is due to the driver library of iGPUs before 11Gen processors don't have the symbols which initial level-zero needed, like `zesInit` , and there is also a bug in `oneapi_init`, `l[i].p` is a pointer to pointer, func ptr stored in `*l[i].p` so we should detect whether `*l[i].p` is null ptr to check whether we load the func successfully. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-24 22:39:02 -05:00
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 pull-request
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#42941
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?