You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the quantization is failed when you build w4a8_mxfp4_fp8 engine using trtllm-build.
RuntimeError: Encounter error 'The value updated is not the same shape as the original. Updated: (5120, 1536), original: (5120, 3072)' for parameter 'transformer.layers.0.attention.qkv.weight'
@youki-sada ,
Thanks for reporting this issue! To help us reproduce and debug the w4a8_mxfp4_fp8 build failure, could you please provide more detailed reproduction steps?
~~~ omitted ~~~
model.layers.27.mlp.down_proj.input_quantizer TensorQuantizer((4, 3) bit fake per-tensor amax=366.0000 calibrator=MaxCalibrator quant)
model.layers.27.mlp.down_proj.output_quantizer TensorQuantizer(disabled)
model.layers.27.mlp.down_proj.weight_quantizer TensorQuantizer((2, 1) bit fake block_sizes={-1: 32, 'type': 'dynamic', 'scale_bits': (8, 0)}, amax=None calibrator=MaxCalibrator quant)
lm_head.input_quantizer TensorQuantizer(disabled)
lm_head.output_quantizer TensorQuantizer(disabled)
lm_head.weight_quantizer TensorQuantizer(disabled) 675 TensorQuantizers found in model
~~~ omitted ~~~
Quantized model exported to :/trt_engines/saved_models_3b_Wf4Af8KVf8. Total time used 7.445543527603149s
########
GPU 0: Peak memory usage = 11.96 GB for all processes on the GPU
GPU 1: Peak memory usage = 0.64 GB for all processes on the GPU
########
@youki-sada , I apologize for the delayed response. I’m trying to understand the current status.
If I’ve understood correctly, you’ve built an engine using NVFP4 x FP8, but it’s not serving because something is not supported yet.
However, the #6809 PR implements NVFP4 x FP8 for the PyTorch backend, not the TensorRT backend.
Therefore, if you were using the old TensorRT workflow, it makes sense that the engine’s execution isn’t supported.
Would you be able to try the PyTorch workflow instead?
Since the 1.0 release, TensorRT LLM has transitioned to the PyTorch workflow, which no longer relies on trtllm-build engines. The team is currently focused on developing this workflow.
@youki-sada ,
Could you please share the command you used to generate the checkpoint '/trt_engines/HF_3b_w4a8_nvfp4_fp8', so that we can easily reproduce the issue?
Activity
Shixiaowei02 commentedon Aug 11, 2025
@Barry-Delaney Could you please reply this issue? Thanks!
karljang commentedon Aug 25, 2025
@youki-sada ,
Thanks for reporting this issue! To help us reproduce and debug the w4a8_mxfp4_fp8 build failure, could you please provide more detailed reproduction steps?
youki-sada commentedon Aug 26, 2025
hf_ptq.py
The checkpoint is successfully exported.
/trt_engines/saved_models_3b_Wf4Af8KVf8/config.jsontrtllm-build
Then, I got following error.
@karljang Any advice would be applicated.
github-actions commentedon Sep 9, 2025
Issue has not received an update in over 14 days. Adding stale label.
youki-sada commentedon Sep 11, 2025
v1.1.0rc4 still have this issue, although it said
Add NVFP4 x FP8in their feature. We tested on following environment.youki-sada commentedon Dec 11, 2025
I successfully built nvfp4 engine of unified HF using v1.2.0rc4, however execution of the engine is not supported yet.
karljang commentedon Dec 11, 2025
@youki-sada , I apologize for the delayed response. I’m trying to understand the current status.
If I’ve understood correctly, you’ve built an engine using NVFP4 x FP8, but it’s not serving because something is not supported yet.
However, the #6809 PR implements NVFP4 x FP8 for the PyTorch backend, not the TensorRT backend.
Therefore, if you were using the old TensorRT workflow, it makes sense that the engine’s execution isn’t supported.
Would you be able to try the PyTorch workflow instead?
Since the 1.0 release, TensorRT LLM has transitioned to the PyTorch workflow, which no longer relies on trtllm-build engines. The team is currently focused on developing this workflow.
Thank you!
youki-sada commentedon Dec 11, 2025
@karljang Thank you for your reply. Yes, I've already tried the Pytorch backend.
karljang commentedon Dec 11, 2025
Hi @QiJune, could you please take a look at the error log above and assist us or assign someone to handle it?
Thank you!
karljang commentedon Dec 11, 2025
@youki-sada ,
Could you please share the command you used to generate the checkpoint
'/trt_engines/HF_3b_w4a8_nvfp4_fp8', so that we can easily reproduce the issue?youki-sada commentedon Dec 11, 2025
I used
nvidia-modelopt==0.39.0.github-actions commentedon Dec 26, 2025
Issue has not received an update in over 14 days. Adding stale label.
github-actions commentedon Jan 9, 2026
This issue was closed because it has been 14 days without activity since it has been marked as stale.