Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Segmentation Fault on ARM-Based Milvus GPU Build (Branch 2.4) #31953

Closed
1 task done
yellow-shine opened this issue Apr 7, 2024 · 2 comments
Closed
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@yellow-shine
Copy link
Collaborator

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: Branch 2.4
- Deployment mode(standalone or cluster): standalone
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): Ubuntu 22.04
- CPU/Memory: 
- GPU: YES
- Others:

Current Behavior

Description:
While attempting to build and run Milvus with GPU support on an ARM-based system, I encountered a "Segmentation fault (core dumped)" error. This issue arose during the execution phase, following a seemingly successful build on the 2.4 branch.

Expected Behavior

Milvus should run without crashing, allowing for further operations and testing.

Steps To Reproduce

Checked out branch 2.4 from the Milvus repository.
Followed the build instructions for an ARM-based system with GPU support.
Executed the Milvus binary.
Encountered the segmentation fault.

Milvus Log

No response

Anything else?

No response

@yellow-shine yellow-shine added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 7, 2024
sre-ci-robot pushed a commit that referenced this issue Apr 7, 2024
issue: #31953

Signed-off-by: yusheng.ma <yusheng.ma@zilliz.com>
@yanliang567
Copy link
Contributor

/assign @samhuang-z
I think @Presburger has merged the fix pr. please help to verify
/unassign

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 8, 2024
Presburger added a commit to Presburger/milvus that referenced this issue Apr 8, 2024
issue: milvus-io#31953

Signed-off-by: yusheng.ma <yusheng.ma@zilliz.com>
Presburger added a commit to Presburger/milvus that referenced this issue Apr 12, 2024
issue: milvus-io#31953

Signed-off-by: yusheng.ma <yusheng.ma@zilliz.com>
Presburger added a commit to Presburger/milvus that referenced this issue Apr 16, 2024
issue: milvus-io#31953

Signed-off-by: yusheng.ma <yusheng.ma@zilliz.com>
sre-ci-robot pushed a commit that referenced this issue Apr 17, 2024
issue: #31953

Signed-off-by: yusheng.ma <yusheng.ma@zilliz.com>
Copy link

stale bot commented May 8, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label May 8, 2024
@stale stale bot closed this as completed May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants