We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
GPU Marketing Name: AMD Radeon Graphics GPU Name: amdgcn-amd-amdhsa--gfx942:sramecc+:xnack- base image: rocm/pytorch-private:vllm0.4.3_06_21_alibaba_fixwvsplitk_ll2_train_csrikris_06_25
chmod +x /usr/local/lib/runTracher.sh cd rocpd_python/ python3 -m pip install . runTracer.sh python3 /workspace/vllm/benchmarks/benchmark_latency.py --model /workspace/Qwen2-7B/ --input-len 32 --output-len 128 --batch-size 16 --dtype float16 --enforce-eager --num-iters-warmup 2 --num-iters 10
... rocpd_op: 0 rocpd_api_ops: 0 rocpd_kernelapi: 0 rocpd_copyapi: 0 rocpd_api: 0 rocpd_string: 0 rpd_tracer: finalized in 1221.910687 ms double free or corruption (!prev) /usr/local/bin/runTracer.sh: line 43: 5233 Aborted (core dumped) LD_PRELOAD=librpd_tracer.so "$@"
there is core dumped error when run tracing. can someone help to verify ? thanks a lot
Ubuntu 20.04.6 LTS (Focal Fossa)
Intel(R) Xeon(R) Platinum 8480C
AMD Instinct MI300X
ROCm 6.1.0
No response
The text was updated successfully, but these errors were encountered:
@mwootton
Sorry, something went wrong.
I am facing this same issue. Was there a resolution for this?
Same issue here. Wondering whether there is a solution?
No branches or pull requests
Problem Description
there is core dumped error when run tracing. can someone help to verify ? thanks a lot
Operating System
Ubuntu 20.04.6 LTS (Focal Fossa)
CPU
Intel(R) Xeon(R) Platinum 8480C
GPU
AMD Instinct MI300X
ROCm Version
ROCm 6.1.0
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: