-
Notifications
You must be signed in to change notification settings - Fork 111
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 Report] Transposed conv2d PCC failures #17647
Comments
Unfortunately, PR #16937 doesn't resolve this issue, |
@pavlepopovic can you use tile layout for output in model until this is fixed and call separate op for untialize? |
sankarmanoj-tt
added a commit
that referenced
this issue
Feb 12, 2025
This is an issue with non_tile_height. Forcing |
pavlejosipovic
pushed a commit
that referenced
this issue
Feb 18, 2025
These two features are non critical for conv2d meaning they don't contribute to enabling any model perf on any model or improve pass rate on any sweep. Problem with these features is that they kick in in very unpredictable conditions for both users and developers as they have many limits/conditions. They are adding to conv2d test matrix, but they are hard to test for as deriving tests that will trigger them on multiple hw platforms is not easy. Moreover they are source of bugs like #17647, and it's often non obvious that bugs originate from these features and when faced with a bug in conv2d first thing is to go to the code and manually disable them to check for that. For the reasons above these will get removed, and by removing them #17647 will be fixed.
4 tasks
pavlejosipovic
pushed a commit
that referenced
this issue
Feb 19, 2025
These two features are non critical for conv2d meaning they don't contribute to enabling any model perf on any model or improve pass rate on any sweep. Problem with these features is that they kick in in very unpredictable conditions for both users and developers as they have many limits/conditions. They are adding to conv2d test matrix, but they are hard to test for as deriving tests that will trigger them on multiple hw platforms is not easy. Moreover they are source of bugs like #17647, and it's often non obvious that bugs originate from these features and when faced with a bug in conv2d first thing is to go to the code and manually disable them to check for that. For the reasons above these will get removed, and by removing them #17647 will be fixed.
pavlejosipovic
pushed a commit
that referenced
this issue
Feb 19, 2025
These two features are non critical for conv2d meaning they don't contribute to enabling any model perf on any model or improve pass rate on any sweep. Problem with these features is that they kick in in very unpredictable conditions for both users and developers as they have many limits/conditions. They are adding to conv2d test matrix, but they are hard to test for as deriving tests that will trigger them on multiple hw platforms is not easy. Moreover they are source of bugs like #17647, and it's often non obvious that bugs originate from these features and when faced with a bug in conv2d first thing is to go to the code and manually disable them to check for that. For the reasons above these will get removed, and by removing them #17647 will be fixed.
pavlejosipovic
pushed a commit
that referenced
this issue
Feb 19, 2025
These two features are non critical for conv2d meaning they don't contribute to enabling any model perf on any model or improve pass rate on any sweep. Problem with these features is that they kick in in very unpredictable conditions for both users and developers as they have many limits/conditions. They are adding to conv2d test matrix, but they are hard to test for as deriving tests that will trigger them on multiple hw platforms is not easy. Moreover they are source of bugs like #17647, and it's often non obvious that bugs originate from these features and when faced with a bug in conv2d first thing is to go to the code and manually disable them to check for that. For the reasons above these will get removed, and by removing them #17647 will be fixed.
dgomezTT
pushed a commit
that referenced
this issue
Feb 19, 2025
These two features are non critical for conv2d meaning they don't contribute to enabling any model perf on any model or improve pass rate on any sweep. Problem with these features is that they kick in in very unpredictable conditions for both users and developers as they have many limits/conditions. They are adding to conv2d test matrix, but they are hard to test for as deriving tests that will trigger them on multiple hw platforms is not easy. Moreover they are source of bugs like #17647, and it's often non obvious that bugs originate from these features and when faced with a bug in conv2d first thing is to go to the code and manually disable them to check for that. For the reasons above these will get removed, and by removing them #17647 will be fixed.
hschoi4448
pushed a commit
that referenced
this issue
Feb 20, 2025
These two features are non critical for conv2d meaning they don't contribute to enabling any model perf on any model or improve pass rate on any sweep. Problem with these features is that they kick in in very unpredictable conditions for both users and developers as they have many limits/conditions. They are adding to conv2d test matrix, but they are hard to test for as deriving tests that will trigger them on multiple hw platforms is not easy. Moreover they are source of bugs like #17647, and it's often non obvious that bugs originate from these features and when faced with a bug in conv2d first thing is to go to the code and manually disable them to check for that. For the reasons above these will get removed, and by removing them #17647 will be fixed.
TT-billteng
pushed a commit
that referenced
this issue
Feb 21, 2025
These two features are non critical for conv2d meaning they don't contribute to enabling any model perf on any model or improve pass rate on any sweep. Problem with these features is that they kick in in very unpredictable conditions for both users and developers as they have many limits/conditions. They are adding to conv2d test matrix, but they are hard to test for as deriving tests that will trigger them on multiple hw platforms is not easy. Moreover they are source of bugs like #17647, and it's often non obvious that bugs originate from these features and when faced with a bug in conv2d first thing is to go to the code and manually disable them to check for that. For the reasons above these will get removed, and by removing them #17647 will be fixed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Transposed Conv2D has PCC failures in shapes we need for a customer model.
PCC issues seem strange, upon runs they remain the same, but following a tt-smi reset, they change (indicative of consuming some uninitialized memory), for example:
Following a tt-smi reset, those change to:
To Reproduce
Attaching unit test here
The text was updated successfully, but these errors were encountered: