Kernel crash when LVDS is enabled in L4T 35.2.1

[Sudar_KB]

Hi All,

We are currently using a customized carrier board that is hosted on the Jetson Xavier NX System on Module (SOM). We are in the process of porting our changes from L4T version 32.4.3 to L4T 35.2.1. Sometimes during the boot process, we have encountered a kernel crash which prevents the device from fully booting up. The device doesn’t boot unless a hard reset is done. We didn’t face this issue in older L4T version 32.4.3. [Note: Our carrier board has LVDS display and HDMI display connected to it] We have included the kernel crash log (kernel_panic_crash_log.txt) for reference. Could you please provide any idea on how to solve this issue.

kernel_panic_crash_log (7.0 KB)

[WayneWWW]

This is a known issue on rel-35 Xavier display.

We have added release note in rel-35.3.1. Please set bootloader-status = “disabled” to the device tree of nvdisplay node.

This will bring boot logo down but you won’t hit kernel panic.

[Sudar_KB]

Hi,
I tried adding the below entries in the tegra194-p3668-common.dtsi file and checked, but i was able to see kernel crash again.

host1x@13e00000 {
nvdisplay@15200000 {
status = “disabled”;
bootloader-status = “disabled”;
};
nvdisplay@15210000 {
status = “disabled”;
bootloader-status = “disabled”;
};
};

Could you please tell if I missed out anything.

[WayneWWW]

If you don’t know how to add device tree or how this thing is doing, please just upgrade to rel-35.3.1.