-
Notifications
You must be signed in to change notification settings - Fork 85
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
Unable to convert Side Aware Boundary Localization: [checkSanity.cpp::checkSanity::106] Error Code 2: Internal Error #112
Comments
The SABL model conversion succeeded on my device with master branch of mmdetection. |
Thanks for your reply. My another conversion for YOLOX seemed to succeeded, but the converted inference model seems not working. Do I need to downgrade the TensorRT 8.4 ea to an earlier version? YOLOX Conversion
YOLOX inference
|
try add cudaDeviceSynchronize(); // synchronize the device so we can read the log
printf("cuda error log: %s\n", cudaGetErrorString(cudaGetLastError())); // print the log before the assert, rebuild the plugin and see if there are any error log. |
cuda error log: the provided PTX was compiled with an unsupported toolchain. |
OK, have you update your cuda or tensorrt? rebuild the plugin library might fix this. |
I have update the cuda development environment to 11.6, and tensorrt is 8.4.0. The plugin is also rebuilt, but the same cuda error still exists.
|
Describe the bug
First, thank you very much for your contribution. When I tried to convert the custom Side-Aware Boundary Localization model, I encountered [checkSanity.cpp::checkSanity::106] Error Code 2: Internal Error. By the way, the custom model works fine when directly use init_detector, inference_detector of mmdet.api.inference. I also found that the implement of SABL in mmdetection 2.12.0 has change a lot compared to 2.19.1. Is the newer version SABL no longer supported? I am beginner of tensorrt and confused with the TRT Error. Could you tell me where the problem exists? Thank you!
Error Output
environment:
The text was updated successfully, but these errors were encountered: