NVIDIA / NVIDIA/TensorRT

Building engine failed of TensorRT 8.6.13 when running on GPU H20

Open
#4,295 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Module:Engine Build triaged
Dominant language
C++
Stars
13.4k
Forks
2.4k
Avg merge
5d 3h
Merged PRs (30d)
2

Description

Description

I tried to run trtexec on GPU H20, but it fails with the error below:

[12/23/2024-09:56:35] [E] Error[2]: Assertion !layerImpls.empty() failed. /motion_head/Atan has no runners that implement it
[12/23/2024-09:56:35] [E] Error[2]: [standardTacticSupply.cpp::getSupportedFormats::37] Error Code 2: Internal Error (Assertion !layerImpls.empty() failed. /motion_head/Atan has no runners that implement it)
[12/23/2024-09:56:35] [E] Engine could not be created from network
[12/23/2024-09:56:35] [E] Building engine failed
[12/23/2024-09:56:35] [E] Failed to create engine from model or file.
[12/23/2024-09:56:35] [E] Engine set up failed

But I can run the same program on the GPU A10. The software versions are exactly the same(I use the same docker). I want to ask what caused this problem? Is it because TensorRT 8613 has different support for the Ampere and Hopper architecture GPUs?

Environment

TensorRT Version:8.6.13

NVIDIA GPU:H20

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported trtexec failure on TensorRT 8.6.13 using the /motion_head/Atan layer, and compare the same container and model on H20 and A10. Check whether the error can be reproduced and whether the differing GPU architecture explains the missing runner; done means identifying a confirmed cause or a documented supported workaround.

Written by the indexing model from the issue text.

Assessment

Domain
machine-learning
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.