Orin nano 4gb hdmi not working after reboot L4T36.4.0 JP6.1

[pippalla.chakravarthi]

Hi Team,

I’m working with a custom board based on the Orin Nano 4GB, and up until recently, the HDMI output was functioning as expected. However, after powering on the system, the HDMI display stopped working. I’ve checked the system via SSH and found the following error logs in dmesg.

I’m wondering if this could indicate a possible issue with the display driver being corrupted or if there is another underlying cause.

[Thu Feb 20 14:11:14 2025] nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for aarch64  540.4.0  Release Build  (buildbrain@mobile-u64-5441-d8000)  Thu Sep 12 21:22:09 PDT 2024
[Thu Feb 20 14:11:14 2025] [drm] [nvidia-drm] [GPU ID 0x00020000] Loading driver
[Thu Feb 20 14:11:14 2025] [drm] Initialized nvidia-drm 0.0.0 20160202 for 13800000.display on minor 1
[Thu Feb 20 14:11:14 2025] checking generic (17de00000 870000) vs hw (17de00000 870000)
[Thu Feb 20 14:11:14 2025] fb0: switching to nvidia-drm from simple
[Thu Feb 20 14:11:14 2025] Console: switching to colour dummy device 80x25
[Thu Feb 20 14:11:14 2025] Console: switching to colour frame buffer device 240x67
[Thu Feb 20 14:11:14 2025] nv_platform 13800000.display: [drm] fb0: nvidia-drmdrmfb frame buffer device
[Thu Feb 20 14:11:14 2025] NVRM nvAssertFailedNoLog: Assertion failed: minRequiredIsoBandwidthKBPS <= clientBwValues[DISPLAY_ICC_BW_CLIENT_EXT].minRequiredIsoBandwidthKBPS @ kern_disp_0402.c:111
[Thu Feb 20 14:11:14 2025] CPU: 0 PID: 9 Comm: kworker/u12:0 Tainted: G           OE     5.15.148-tegra #2
[Thu Feb 20 14:11:14 2025] Hardware name: NVIDIA Rapyuta Robotics Version 2.0/Jetson, BIOS 36.4.0-gcid-37537400 09/13/2024
[Thu Feb 20 14:11:14 2025] Workqueue: dce-async-ipc-wq dce_client_async_event_work [tegra_dce]
[Thu Feb 20 14:11:14 2025] Call trace:
[Thu Feb 20 14:11:14 2025]  dump_backtrace+0x0/0x1c0
[Thu Feb 20 14:11:14 2025]  show_stack+0x34/0x50
[Thu Feb 20 14:11:14 2025]  dump_stack_lvl+0x68/0x84
[Thu Feb 20 14:11:14 2025]  dump_stack+0x18/0x34
[Thu Feb 20 14:11:14 2025]  os_dump_stack+0x1c/0x28 [nvidia]
[Thu Feb 20 14:11:14 2025]  tlsEntryGet+0x110/0x120 [nvidia]
[Thu Feb 20 14:11:14 2025]  kdispArbAndAllocDisplayBandwidth_v04_02+0x274/0x290 [nvidia]
[Thu Feb 20 14:11:14 2025]  kdispInvokeDisplayModesetCallback_KERNEL+0xa8/0xf0 [nvidia]
[Thu Feb 20 14:11:14 2025]  hypervisorIsVgxHyper_IMPL+0x144/0x260 [nvidia]
[Thu Feb 20 14:11:14 2025]  dce_client_async_event_work+0x90/0x190 [tegra_dce]
[Thu Feb 20 14:11:14 2025]  process_one_work+0x208/0x4d0
[Thu Feb 20 14:11:14 2025]  worker_thread+0x144/0x490
[Thu Feb 20 14:11:14 2025]  kthread+0x184/0x190
[Thu Feb 20 14:11:14 2025]  ret_from_fork+0x10/0x20
[Thu Feb 20 14:11:15 2025] wlP1p1s0: authenticate with cc:88:c7:fe:8b:b1
[Thu Feb 20 14:11:15 2025] wlP1p1s0: send auth to cc:88:c7:fe:8b:b1 (try 1/3)
[Thu Feb 20 14:11:15 2025] wlP1p1s0: authenticated
[Thu Feb 20 14:11:15 2025] wlP1p1s0: associate with cc:88:c7:fe:8b:b1 (try 1/3)
[Thu Feb 20 14:11:15 2025] wlP1p1s0: RX AssocResp from cc:88:c7:fe:8b:b1 (capab=0x11 status=0 aid=3)
[Thu Feb 20 14:11:15 2025] wlP1p1s0: associated
[Thu Feb 20 14:11:15 2025] IPv6: ADDRCONF(NETDEV_CHANGE): wlP1p1s0: link becomes ready
[Thu Feb 20 14:11:38 2025] NVRM nvCheckFailedNoLog: Check failed: CliGetEventInfo(rpc_params->hClient, rpc_params->hEvent, &pEvent) @ dce_client_rpc.c:337
[Thu Feb 20 14:11:41 2025] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00020000] Flip event timeout on head 0
[Thu Feb 20 14:11:45 2025] NVRM nvCheckFailedNoLog: Check failed: CliGetEventInfo(rpc_params->hClient, rpc_params->hEvent, &pEvent) @ dce_client_rpc.c:337
[Thu Feb 20 14:11:49 2025] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00020000] Flip event timeout on head 0
[Thu Feb 20 14:11:49 2025] usb 1-1: USB disconnect, device number 2
[Thu Feb 20 14:11:49 2025] usb 1-1.3: USB disconnect, device number 4
[Thu Feb 20 14:11:49 2025] usb 1-1.4: USB disconnect, device number 6
[Thu Feb 20 14:12:16 2025] NVRM nvCheckFailedNoLog: Check failed: CliGetEventInfo(rpc_params->hClient, rpc_params->hEvent, &pEvent) @ dce_client_rpc.c:337
[Thu Feb 20 14:12:19 2025] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00020000] Flip event timeout on head 0
[Thu Feb 20 14:12:21 2025] NVRM nvCheckFailedNoLog: Check failed: CliGetEventInfo(rpc_params->hClient, rpc_params->hEvent, &pEvent) @ dce_client_rpc.c:337
[Thu Feb 20 14:12:24 2025] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00020000] Flip event timeout on head 0
[Thu Feb 20 14:12:51 2025] NVRM nvCheckFailedNoLog: Check failed: CliGetEventInfo(rpc_params->hClient, rpc_params->hEvent, &pEvent) @ dce_client_rpc.c:337
[Thu Feb 20 14:12:54 2025] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00020000] Flip event timeout on head 0
[Thu Feb 20 14:13:18 2025] NVRM nvCheckFailedNoLog: Check failed: CliGetEventInfo(rpc_params->hClient, rpc_params->hEvent, &pEvent) @ dce_client_rpc.c:337
[Thu Feb 20 14:13:21 2025] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00020000] Flip event timeout on head 0
[Thu Feb 20 14:13:40 2025] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[Thu Feb 20 14:13:40 2025] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL P2422H (HDMI-0)
[Thu Feb 20 14:13:41 2025] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[Thu Feb 20 14:13:41 2025] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[Thu Feb 20 14:13:42 2025] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[Thu Feb 20 14:13:42 2025] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[Thu Feb 20 14:13:43 2025] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[Thu Feb 20 14:13:43 2025] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[Thu Feb 20 14:13:44 2025] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[Thu Feb 20 14:13:44 2025] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[Thu Feb 20 14:13:44 2025] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[Thu Feb 20 14:13:44 2025] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[Thu Feb 20 14:13:45 2025] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[Thu Feb 20 14:13:45 2025] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[Thu Feb 20 14:13:46 2025] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[Thu Feb 20 14:13:46 2025] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[Thu Feb 20 14:13:47 2025] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[Thu Feb 20 14:13:47 2025] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[Thu Feb 20 14:13:47 2025] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[Thu Feb 20 14:13:47 2025] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[Thu Feb 20 14:13:48 2025] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[Thu Feb 20 14:13:48 2025] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0

Thanks

[WayneWWW]

A “sudden happened” issue could indicate a hardware defect. I would suggest you should reflash the board and make sure the software is clean first.

[pippalla.chakravarthi]

Thank you for the suggestion. I understand that a sudden issue could indicate a hardware defect, but just to clarify, when I mentioned “sudden,” I meant it started happening without any changes or physical tampering to the hardware. After reflashing, the system is working again, but I’m still curious as to why the issue appeared in the first place.

[WayneWWW]

please do more test on your side and see if you could locate the reason to trigger this error.

In the meantime, actually you could also upgrade to rel-36.4.3 as I know some display patches are present on that version.

[pippalla.chakravarthi]

Thanks for the suggestion. I tested with version 36.4.0 and didn’t encounter the issue again, but now I’m facing a problem where HDMI hotplug is not working

[WayneWWW]

You have to make sure all the necessary software patches are still present there (e.g. hpg gpio in DT).

[pippalla.chakravarthi]

Hi @WayneWWW ,

I checked with fdtdump the hpg gpio is present in DTb aswell as dts source too

[WayneWWW]

Please check p3509+p3767 board config file in your Linux_for_Tegra BSP directory. Make sure all the items mentioned there are all present in your flash board cofnig.

Display related things are not just in the kernel DT. Checking kernel DT only is not sufficient.

[pippalla.chakravarthi]

Hi Wayne,

After changing the HDMI_HPD pin entry from output to input in the GPIO pinmux DTSI file, hotplugging started working. It’s strange that in Jetpack 5.1.2, this didn’t cause any issues, but in Jetpack 6.1, it’s now working.