-
Notifications
You must be signed in to change notification settings - Fork 35
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
invalid output with gfx803 and BUILD_WITH_TENSILE_HOST ON #4
Comments
Thank @https://github.com/cgmb to show how to use rocblas-test to verify the issue of rocblas on gfx803. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Finally, I can reproduce gfx803 with BUILD_WITH_TENSILE_HOST errors using a small sample.
test codes : https://github.com/xuhuisheng/rocm-build/blob/feature/check/check/test-pytorch-rocblas.py
In this code, there is one full connection layer
Y = w0 * x0 + w1 * x1 + b
For simple case, I init weight with [1,1], bias with 10, so it should not change anything, loss always should be 0.
But on the 12th steps, loss changed to 50. It is reproducable on my computer.
I print the X, Y, output, loss, and find out that the first 16 of output is 12 which is correct. the last 12 of output is 2 which is wrong. And seems the last 16 of output miss the bias, I guess.
If I used BUILD_WITH_TENSILE_HOST=OFF and re-compile rocBLAS, the error will gone.
And It is weired if I comment out
l.backward()
, the error will change to happen on 21th step, and output change to all 3.Why it is unstable? Maybe gfx803 need PCI3 Atomics operation? or gfx803 just miss some waitcnt() instructions?
So I believe it caused by the new Tensile client which used assembly codes to optimized. I am not familiar with GCN assemly, So I create an issue to tensile wish someone could help.
ROCm/Tensile#1287
The text was updated successfully, but these errors were encountered: