-
Notifications
You must be signed in to change notification settings - Fork 236
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][GFX1030] Random Memory access faults on gfx1030. #1613
Labels
Comments
@atamazov FYI |
I'll try to look into this. |
log info
|
It looks like the issue has been solved, let me close this issue. |
Not fixed! |
Sorry for that. Also pin it back. |
So is there a way to solve this problem? |
@shurale-nkn Is it possible to reliably reproduce the issue? |
@shurale-nkn Is this fixed with latest ROCm 6.0.2 (HIP 6.0.32831)? Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[Keywords]:
test; gfx1030;
[Description]:
Random Memory access faults on gfx1030.
5 different PRs failed at a random stage, but always with gfx1030.
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/test-int8-mlir-nonxdlops/2/pipeline
log info
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/int8-perf-config-tuning/16/pipeline
log info
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/int8-perf-config-tuning/17/pipeline/625
log info
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/jd%2Fck_integration/64/pipeline/255
log info
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/jd%2Fck_integration/67/pipeline/310
log info
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/dfeng_int8_quantization_api/2/pipeline/1554
log info
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/fix_1549/7/pipeline/1640
log info
http://micimaster.amd.com/blue/organizations/jenkins/MLLibs%2FMIOpen/detail/fix_1549/9/pipeline/625
log info
The text was updated successfully, but these errors were encountered: