[Bug][AutoDeploy]: Llama3.2 Vision models fail - exported model signature mismatch for use_cache/return_dict
Open
@bmarimuthu-nv is already working on this.
Since Jan 6, 2026.
AutoDeploy
bug
triaged
- Dominant language
- Python
- Stars
- 14.7k
- Forks
- 2.8k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 489
Description
System Info
H100
Who can help?
No response
Information
- The official example scripts
- My own modified scripts
Tasks
- An officially supported task in the
examplesfolder (such as GLUE/SQuAD, ...) - My own task or dataset (give details below)
Reproduction
python3 /opt/tensorrt-llm/examples/auto_deploy/build_and_run_ad.py --model meta-llama/Llama-3.2-11B-Vision-Instruct --args.yaml-extra
/opt/tensorrt-llm/examples/auto_deploy/model_registry/configs/dashboard_default.yaml --args.yaml-extra /opt/tensorrt-llm/examples/auto_deploy/model_registry/configs/world_size_2.yaml
Expected behavior
Model should build and run
actual behavior
TypeError: MllamaForCausalLM.__init__() got an unexpected keyword argument 'use_cache'
additional notes
When exporting vision models (e.g., meta-llama/Llama-3.2-11B-Vision-Instruct), setting use_cache=False and return_dict=False during export to avoid DynamicCache issues causes these parameters to be included in the exported model signature. At runtime, cm.named_args doesn't include
them, leading to a keyword mismatch error.
Before submitting a new issue...
- Make sure you already searched for relevant issues, and checked the documentation and examples for answers to frequently asked questions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.