Close nvcsi stream leads to NULL pointer dereference in kernel in driveos 5.2.0

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
[√] DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version

Target Operating System
[√] Linux

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
[√] NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)

SDK Manager Version

Host Machine Version
[√] native Ubuntu 18.04

Ref: V4L2 timeout leads to NULL pointer dereference in kernel in jetpack 4.6

When vi report error message as below:

we try to close the camera sensor, but fails with the error message:

Sometimes the kernel will reboot suddenly, .

Is this the known issue in driveos 5.2.0? How can we fix this problem?

Are you using DRIVE or Jetson platform? For DRIVE, please utilize NvMedia or DriveWorks APIs instead of V4L2.

We use the drive platform and use the NvMedia APIs. I would like to know if there is this issue on the drive platform.

I don’t have the 5.2.0 source code on hand. Please check the capture.c file located at /home/jikuo/nvidia/nvidia_sdk/*/DRIVEOS/drive-oss-src/nvidia/drivers/media/platform/tegra/camera/vi/.

we can not find the capture.c file in your mentioned path. BTW, i find a similar capture-vi.c located at driveos/drive-oss-src/nvidia/drivers/media/platform/tegra/camera/fusa-capture/capture-vi.c. Could you help to find out if the problem exists?

It was also merged into our main branch so please go ahead to apply the patch.

Do you know why there was no call stack written in /var/log/syslog file when the problem happened? We only saw this error log, but no call stack.

I’m uncertain whether the absence of the call stack in the /var/log/syslog file is caused by specific logging configurations or another factor. To investigate, you can try invoking the same logging function that produces messages visible in the /var/log/syslog file.