NVIDIA / NVIDIA/TensorRT

could not find any supported formats consistent with input/output data types failure of TensorRT 10.3 on jetson orin

Open
#4,217 2 comments 0 reactions 1 assignee View on GitHub

@yuanyao-nv is already working on this.

Since Feb 11, 2025.

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

Description

Description

The following error occurred during the process of converting the onnx file to engine on jetson orin. For specific logs, see the attached file log.txt

The execution command is
/usr/src/tensorrt/bin/trtexec --onnx=/home/orin/disk/lhg/BEVFormer_tensorrt/checkpoints/onnx/bevformer_small_epoch_24_cp.onnx --saveEngine=bevformer_small_epoch_24_cp.engine --fp16 --int8 --plugins=./TensorRT/lib/libtensorrt_ops.so

The error message is
‘ IBuilder::buildSerializedNetwork: Error Code 9: Internal Error (node_of_onnx::Shape_2609: could not find any supported formats consistent with input/output data types)’

When I use tensorrt8.6, the above error does not occur. So I think it may be strongly related to tensorrt version.

Environment

TensorRT Version: 10.3

NVIDIA GPU: jetson orin

CUDA Version:12.2

Jetpack Version:12.2

Operating System: 22.04

Baremetal or Container (if so, version): nvcr.io/nvidia/l4t-jetpack:r36.4.0

Relevant Files

Model link:https://drive.google.com/file/d/1N98z1DIDiy6Z5_Sfa-vFvrTGXPkmUIrq/view?usp=sharing

Steps To Reproduce

  1. Pull the image https://catalog.ngc.nvidia.com/orgs/nvidia/containers/l4t-jetpack/tags
  2. The custom plugin is compiled to generate libtensorrt_ops.so.
  3. /usr/src/tensorrt/bin/trtexec --onnx=/home/orin/disk/lhg/BEVFormer_tensorrt/checkpoints/onnx/bevformer_small_epoch_24_cp.onnx --saveEngine=bevformer_small_epoch_24_cp.engine --fp16 --int8 --plugins=./TensorRT/lib/libtensorrt_ops.so

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.