We’re using a custom carrier board for the 16GB Jetson Orin Nano and are having issues with some devices’ HDMI output to a TV. We’re using x11. The symptom, other than no HDMI display, is that xrandr (and other x commands) hang indefinitely. In dmesg, we get errors around nvidia-modeset and then the last error repeats:
Jun 10 17:55:57 jetson kernel: [ 143.429933] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing. Jun 10 17:56:29 jetson kernel: [ 175.435480] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000c67d:0:0:1107 Jun 10 17:56:45 jetson kernel: [ 191.436195] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000c67e:2:0:1116 Jun 10 17:56:53 jetson kernel: [ 199.436552] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000c67e:3:0:1116 Jun 10 17:57:01 jetson kernel: [ 207.437040] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000c67d:0:0:1107 Jun 10 17:57:17 jetson kernel: [ 223.437722] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000c67e:2:0:1116 Jun 10 17:57:25 jetson kernel: [ 231.438094] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000c67e:3:0:1116 Jun 10 17:57:33 jetson kernel: [ 239.439270] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000c67d:0:0:1107 Jun 10 17:57:49 jetson kernel: [ 255.439993] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000c67e:2:0:1116 Jun 10 17:57:57 jetson kernel: [ 263.440459] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000c67e:3:0:1116 Jun 10 17:58:18 jetson kernel: [ 284.537346] nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67e:2 2:0:2612:2600 Jun 10 17:58:23 jetson kernel: [ 289.537362] nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67e:2 2:0:2612:2600
Happy to provide any logs or information that would be useful.
Did you already configure the software from default DP mode to HDMI mode before this?
We included tegra234-dcb-p3767-0000-hdmi.dtbo in the board conf file if that’s what you mean. xrandr gives
Screen 0: minimum 8 x 8, current 1280 x 720, maximum 32767 x 32767
HDMI-0 connected primary 1280x720+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm
1920x1080 60.00 + 60.00 59.99 59.94 29.97 23.98
Another dmesg error that seems to occur with the previously mentioned errors is
[ 13.574657] nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for aarch64 540.3.0 Release Build (buildbrain@mobile-u64-6367-d8000) Mon May 6 10:21:06 PDT 2024
[ 14.278228] NVRM nvAssertFailedNoLog: Assertion failed: minRequiredIsoBandwidthKBPS <= clientBwValues[DISPLAY_ICC_BW_CLIENT_EXT].minRequiredIsoBandwidthKBPS @ kern_disp_0402.c:111
[ 14.278238] CPU: 2 PID: 328 Comm: kworker/u16:5 Tainted: G OE 5.15.136-tegra #1
[ 14.278243] Hardware name: NVIDIA Artisight V3 Orin NX 16GB/Jetson, BIOS 202402.1-81336553-dirty 01/16/2025
[ 14.278246] Workqueue: dce-async-ipc-wq dce_client_async_event_work [tegra_dce]
[ 14.278271] Call trace:
[ 14.278272] dump_backtrace+0x0/0x1c0
[ 14.278282] show_stack+0x34/0x50
[ 14.278287] dump_stack_lvl+0x68/0x84
[ 14.278293] dump_stack+0x18/0x34
[ 14.278296] os_dump_stack+0x1c/0x28 [nvidia]
[ 14.278439] nvAssertFailedBacktrace.part.0+0x80/0x90 [nvidia]
[ 14.278564] kdispArbAndAllocDisplayBandwidth_v04_02+0x274/0x290 [nvidia]
[ 14.278688] kdispInvokeDisplayModesetCallback_KERNEL+0xa8/0xf0 [nvidia]
[ 14.278827] osTegraDceClientIpcCallback+0x84/0xb0 [nvidia]
[ 14.279030] dce_client_async_event_work+0x90/0x190 [tegra_dce]
[ 14.279048] process_one_work+0x208/0x4d0
[ 14.279056] worker_thread+0x144/0x490
[ 14.279061] kthread+0x184/0x190
[ 14.279065] ret_from_fork+0x10/0x20
Please share me the full xorg log.
The log you just posted won’t cause any fatal issue. That is normal warning.
You should try to give out a method that can reproduce the first error you posted.
Great to know that’s a normal warning. Attached is the xorg log.
Xorg.0.log (13.1 KB)
One thing we noticed is we only see this on 4k TVs, and on the ones that don’t work, if we add to xorg.conf
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Tegra0"
SubSection "Display"
Depth 24
Virtual 1920 1080 # Modify to set the max resolution
EndSubSection
EndSection
the error does not occur. So it points to an issue with 4k displays.