Nvargus-daemon crash issue

[xinghui.g]

Hi Nvidia，

When we boot up the system, we got a system error saying that the argus process has crashed.

SDK info is:
R36 (release), REVISION: 3.0, GCID: 36191598, BOARD: generic, EABI: aarch64, DATE: Mon May 6 17:34:21 UTC 2024

Stacktrace is:

#0  0x0000ffff8ac32634 in ?? () from /usr/lib/aarch64-linux-gnu/nvidia/libnvargus_socketserver.so
No symbol table info available.
#1  0x0000ffff8ac327ac [PAC] in ?? () from /usr/lib/aarch64-linux-gnu/nvidia/libnvargus_socketserver.so
No symbol table info available.
#2  0x0000ffff8ac38114 [PAC] in ?? () from /usr/lib/aarch64-linux-gnu/nvidia/libnvargus_socketserver.so
No symbol table info available.
#3  0x0000ffff8ac51180 [PAC] in ?? () from /usr/lib/aarch64-linux-gnu/nvidia/libnvargus_socketserver.so
No symbol table info available.
#4  0x0000ffff8ac51634 [PAC] in ?? () from /usr/lib/aarch64-linux-gnu/nvidia/libnvargus_socketserver.so
No symbol table info available.
#5  0x0000ffff8ac5187c [PAC] in ?? () from /usr/lib/aarch64-linux-gnu/nvidia/libnvargus_socketserver.so
No symbol table info available.
#6  0x0000ffff8ac50aac [PAC] in ?? () from /usr/lib/aarch64-linux-gnu/nvidia/libnvargus_socketserver.so
No symbol table info available.
#7  0x0000ffff8ac50c90 [PAC] in ?? () from /usr/lib/aarch64-linux-gnu/nvidia/libnvargus_socketserver.so
No symbol table info available.
#8  0x0000ffff8a9cd5c8 [PAC] in start_thread (arg=0x0) at ./nptl/pthread_create.c:442
        ret = <optimized out>
        pd = 0x0
        out = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {281472749140032, 281474962531720, 281474962531406, 8433792, 281474962531407, 0, 281472740704256, 8433792, 281473008511040, 281472740704256, 281472749137760, 3008897975949569003, 0, 3008897976731472023, 0, 0, 0, 0, 0, 0, 0, 0}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
        not_first_call = 0
#9  0x0000ffff8aa35edc in thread_start () at ../sysdeps/unix/sysv/linux/aarch64/clone.S:79
No locals.

[carolyuu]

Hi,

For the camera basic functionality first needs to check the device and driver configuration.
You can reference to below program guide for the detailed information of device tree and driver implementation.
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/SD/CameraDevelopment/SensorSoftwareDriverProgramming.html?highlight=programing#sensor-software-driver-programming

Please refer to Applications Using V4L2 IOCTL Directly by using V4L2 IOCTL to verify basic camera functionality.
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/SD/CameraDevelopment/SensorSoftwareDriverProgramming.html?highlight=programing#to-run-a-v4l2-ctl-test

Once confirm the configure and still failed below link help to get log and some information and some tips for debug.
https://elinux.org/Jetson/l4t/Camera_BringUp#Steps_to_enable_more_debug_messages

Thanks!

[JerryChang]

hello xinghui.g,

is it a must to stay-on JP-6.0/r36.3 public release? since the latest release is JetPack 6.2/L4T 36.4.3.

anyways, may I have more details of your environment setup.
for instance, which camera sensor it is. had you validate the camera driver on any previous Jetpack release…etc?

[xinghui.g]

Hi JerryChang,

Will the latest release: JetPack 6.2/L4T 36.4.3 fix the crashing issue?

At the time of the crash, we didn’t using the camera actually.

FYI, Camer sensor is ISX031. For more details refer to [R36.3] Can't capture images successfully with ISX031, Need some help

[JerryChang]

hello xinghui.g,

I assume you’re based-on IMX219 reference driver to develop your sensor driver.
and… such failure caused by sensor registration during kernel initial progress, right?

[xinghui.g]

Hi JerryChang,

We are debugging, the camera driver needs to be installed manually ( sudo insmod nv_isx031.ko), and at the time of the crash, it wasn’t installed yet.

[JerryChang]

hello xinghui.g,

however, I don’t see such failure on reference board.
please check whether you’ll seeing the same by moving to r36.4.3