You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. I have searched related issues but cannot get the expected help.
2. The bug has not been fixed in the latest version.
3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.
5. Please use English, otherwise it will be closed.
Describe the bug
I am running DeepSeek v3 on a node with 8xMI300X GPUs on ROCm 6.3.1. I am able to run it using an image built from Dockerfile.rocm in docker, however I have noticed this warning show up:
Using default W8A8 Block FP8 kernel config. Performance might be sub-optimal! Config file not found at <multiple config files>
In the container built from Dockerfile.rocm, with SGLang v0.4.2, these are the missing config files:
I also tried the Docker image lmsysorg/sglang:v0.4.1.post4-rocm620, based on this blog from AMD. This had SGLang v0.4.1, and was missing the following config files:
Checklist
Describe the bug
I am running DeepSeek v3 on a node with 8xMI300X GPUs on ROCm 6.3.1. I am able to run it using an image built from
Dockerfile.rocm
indocker
, however I have noticed this warning show up:In the container built from
Dockerfile.rocm
, with SGLang v0.4.2, these are the missing config files:I also tried the Docker image
lmsysorg/sglang:v0.4.1.post4-rocm620
, based on this blog from AMD. This had SGLang v0.4.1, and was missing the following config files:Reproduction
Reproduction steps:
I launched the container with the command:
And I ran the server using the command
Environment
ROCm 6.3.1
8xMI300X
Docker images:
v0.4.2-rocm620:latest
built fromdocker/Dockerfile.rocm
and build instructions from SGLang docslmsysorg/sglang:v0.4.1.post4-rocm620
The text was updated successfully, but these errors were encountered: