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
I need to run GEMM for the configuration M×N×K=216000×4608×1152 in the example/01_gemm directory. To make this configuration compile successfully, I've adjusted the block size to 384. Although this change allows compilation, running the configuration results in an "unspecified launch failure." It appears that using any block size other than 256 or other powers of two greater than 256 triggers this error. Could you confirm if this limitation exists, and if so, could you provide an example of parameters that would work for this configuration? Here are my current parameter settings:
Hi @cognaiger9. Yes despite the parameters such as block size being exposed, many of them are not meant to be modified by end users since they are hardware/algorithm specific (as per #630). Please use existing kernel instances's parameters for block size and M, N, K per block parameters. Thanks!
Problem Description
I need to run GEMM for the configuration M×N×K=216000×4608×1152 in the
example/01_gemm
directory. To make this configuration compile successfully, I've adjusted the block size to 384. Although this change allows compilation, running the configuration results in an "unspecified launch failure." It appears that using any block size other than 256 or other powers of two greater than 256 triggers this error. Could you confirm if this limitation exists, and if so, could you provide an example of parameters that would work for this configuration? Here are my current parameter settings:Operating System
Ubuntu 20.04.6 LTS (Focal Fossa)
CPU
AMD EPYC 7413 24-Core Processor
GPU
AMD Instinct MI250X
Other
No response
ROCm Version
ROCm 6.0.0
ROCm Component
Composable Kernel
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: