Uefi display handoff to efifb, system crash

Robotics & Edge Computing Jetson Systems Jetson Thor
,
1

hi nvidia

uefi display handoff to efifb, system crash!

JetPack_7.0_Linux_JETSON_AGX_THOR_TARGETS

kernel: R38.2.1

SOC Display Hand-off Mode

SOC Display Hand-off

cat /etc/nv_tegra_release

R38 (release), REVISION: 2.1, GCID: 42061081, BOARD: generic, EABI: aarch64, DATE: Wed Sep 10 19:49:31 UTC 2025

KERNEL_VARIANT: oot

TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia
INSTALL_TYPE=openrm

uefi-display-handoff-to-efifb-crash.txt (165.8 KB)

3

Hi helianyi1,

Are you using the devkit or custom board for Thor?

localhost login: [   24.294374] dce: dce_client_ipc_wait:378  Client [0] unexpected err: [-110]
[   24.294398] dce: dce_ipc_send_message_sync:554  Error in waiting for ack
[   34.534362] dce: dce_client_ipc_wait:378  Client [0] unexpected err: [-110]
[   34.534369] dce: dce_ipc_send_message_sync:554  Error in waiting for ack
[   34.542328] [drm:nv_drm_exit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00020000] Failed to allocate NvKmsKapiDevice
[   34.542539] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000018
[   34.544869] [drm:nv_drm_register_drm_device [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00020000] Failed to load device
[   34.553619] Mem abort info:

Do you connect the DP display at this moment?
If so, would you hit the similar issue if you disconnect the display?

4

hi nvidia:

I am using devkit

I connect HDMI display at this moment

if I disconnect the display, dont hit this issue.

5

Could you provide the steps to reproduce this issue?
and how about the failed rate?

6

thor-efifb
thor-efifb844×526 189 KB
then F10 –>Esc–>continue–>enter,100% hit this issue

7

Thanks for the steps. Please let me verify it locally and get back to you.

Is the issue specific to HDMI? (i.e. would you hit the issue if you connect DP instead of HDMI)

8

dp-efifb-crash.txt (162.9 KB)

hi nvidia:

I connect DP monitor, also 100% hit this issue .

11

Hi helianyi1,

We can reproduce it on the devkit.
I’m checking this issue with internal and will keep you updated.

12

Hi helianyi1,

I’ve checked this with internal.
The current L4T does not support EFIFB and we will remove the option in later release.
Please use simple-framebuffer on Thor instead.

13

hi nvidia:

can enable simple-framebuffer in dts when next release ?

14

Yes, the following node will be added in the next Jetpack 7 release and you can simply enable it through updating the status property.

                framebuffer {
                        compatible = "simple-framebuffer";
-                       status = "disabled";
+                       status = "okay";
                        memory-region = <0x23c>;
                        power-domains = <0x02 0x01>;
                        #power-domain-cells = <0x01>;
                        ..
15

thanks

16

I found that you don’t need to update device tree manually.
It will be updated dynamically by UEFI when it enables display and handsoff display.

# With DP display connected
[    0.000000] OF: reserved mem: 0x0000001fd8000000..0x0000001fd8b3ffff (11520 KiB) nomap non-reusable framebuffer@1F,D8000000
[    5.477587] [drm] Initialized simpledrm 1.0.0 20200625 for chosen:framebuffer on minor 0
[    5.493283] simple-framebuffer chosen:framebuffer: [drm] fb0: simpledrmdrmfb frame buffer device
# Without display connected
[   13.094347] [drm] [nvidia-drm] [GPU ID 0x00020000] Invalid framebuffer console info

As a result, please wait for the next Jetpack 7 release to verify.