Linux kernel crash when CONFIG_DEBUG_PREEMPT is enabled

We are using Jetson AGX orin 64GB developer kit. We are updating the kernel image with preempt_rt support. As part of the migration, I have enabled the CONFIG_DEBUG_PREEMPT=y to print warnings if kernel code uses it in a preemption-unsafe way and in the default nvidia kernel config CONFIG_DEBUG_PREEMPT is not set. When this configuration is enabled, i am seeing below kernel call trace in the bootup. What could be the reason this call trace?

CPU: 5 PID: 190 Comm: kworker/u24:1 Tainted: G W 5.15.178-rt76-yocto-preempt-rt #1
Hardware name: NVIDIA NVIDIA Jetson AGX Orin Developer Kit/Jetson, BIOS 36.3.0-gcid-36191598 05/06/2024
Workqueue: events_unbound deferred_probe_work_func
Call trace:
dump_backtrace+0x0/0x1d0
show_stack+0x20/0x30
dump_stack_lvl+0x64/0x80
dump_stack+0x18/0x34
check_preemption_disabled+0x11c/0x130
debug_smp_processor_id+0x20/0x30
gic_cpu_init+0x2c/0x130
gic_init_bases+0x1d4/0x280
gic_of_init_child+0x13c/0x250
gic_probe+0x13c/0x260
platform_probe+0x70/0xd0
really_probe.part.0+0xa4/0x310
__driver_probe_device+0xa0/0x174
driver_probe_device+0x48/0x17c
__device_attach_driver+0xc0/0x150
bus_for_each_drv+0x84/0xe0
__device_attach+0xa4/0x1a0
device_initial_probe+0x1c/0x2c
bus_probe_device+0xa4/0xb0
device_add+0x3a8/0x8cc
of_device_add+0x4c/0x70
of_platform_device_create_pdata+0xa0/0x134
of_platform_bus_create+0x15c/0x3b4
of_platform_populate+0x58/0x104
tegra_aconnect_probe+0x9c/0x110
platform_probe+0x70/0xd0
really_probe.part.0+0xa4/0x310
__driver_probe_device+0xa0/0x174
driver_probe_device+0x48/0x17c
__device_attach_driver+0xc0/0x150
bus_for_each_drv+0x84/0xe0
__device_attach+0xa4/0x1a0
device_initial_probe+0x1c/0x2c
bus_probe_device+0xa4/0xb0
deferred_probe_work_func+0x90/0xd0
process_one_work+0x200/0x500
worker_thread+0x218/0x4b0
kthread+0x19c/0x1ac
ret_from_fork+0x10/0x20
gic 2a41000.interrupt-controller: GIC IRQ controller registered
tegra-aconnect bus@0:aconnect@2900000: Tegra ACONNECT bus registered
gpio-394 (camera-control-output-low): hogged as output/low

Thanks,
Rajesh

Hi,
Looks like you use Yocto rootfs. Please try sample Ubuntu rootfs and see if the issue is still present. And looks like you use r36.3 and may try r36.4(Jetpack 6.1).