-
Notifications
You must be signed in to change notification settings - Fork 237
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
[MI100][FP32] ConvHipImplicitGemmBwdDataV4R1Xdlops verficiation failure (SWDEV-305815) #1206
Comments
W/A for 4.5 release is provided. Now we need to provide W/A for develop. Explanations tomorrow. |
Urgency shall be lowered after #1208 is merged in. |
Link to Jira added. |
AnalysisThe precision degradation occurs with certain values of PerformanceConfig -- 9 out of 111 total. The degradation seems so high (7 orders of magnitude) that I can't suppose that the reason is rounding or order-of-computations differences between CPU and GPU. Most likely reason is that the Solver does not comply to the #866 (comment), specifically:
Excerpt from the full table of PerformanceConfigs:
Full table of PerformanceConfigs and results[Click to view]
Console log and how to reproduceissue-1206-MI100-rocm4.3.1-console-log.zip Use the
|
This comment has been minimized.
This comment has been minimized.
#1206 (comment) moved to #1208 (comment) |
… Disable ConvHipImplicitGemmBwdDataV4R1Xdlops for FP32.
@atamazov SWDEV-305815 is closed. Can we close this ticket as well? Thanks! |
Related Jira: https://ontrack-internal.amd.com/browse/SWDEV-305815
Reproducible with 4.3.1.
Failing config:
The root reason is precision issue of ConvHipImplicitGemmBwdDataV4R1Xdlops (or precision issue of the verification in the driver, which is unlikely IMO).
The implicit reason of the issue is the recent find-db update (#1196) which moved ConvHipImplicitGemmBwdDataV4R1Xdlops on top of the list (it is the fastest one).
Most likely the same issue persists in 4.5 release staging branch as it contains #1195 (which is expected to be identical to #1196)
System find-db reports the following:
How to reproduce independently of find-db contents: Append
-S 60
to the driver command line (so the driver will use Immediate mode withConvHipImplicitGemmBwdDataV4R1Xdlops
) or prepend the driver command withMIOPEN_DEBUG_FIND_ONLY_SOLVER=ConvHipImplicitGemmBwdDataV4R1Xdlops MIOPEN_FIND_MODE=normal
.I am investigating this.
The text was updated successfully, but these errors were encountered: