Kernel Panic Problem

jetpack5.1.3
Tests have found that these two errors occurring at the same time can cause a kernel panic, resulting in a restart. Is there a way to stop the panic?
First, turn on the camera to print a lot of “tegra-camrtc-capture-vi”, then unplug the camera, start print"[346.849751] (NULL device *): vi_capture_control_message: NULL VI channel received
[346.849757] t194-nvcsi 13e10000. host1x:nvcsi@15a00000: csi5_stream_close: Error in0 ". After about one or two minutes, the kernel panic, and then the system restart
I hope there is no panic causing the reboot and no need to fix the bug
This is dmesg
dmesg.txt (123.9 KB)

hello Seven0,

this is failure reported by VI since it’s not recognize valid camera node.

are you developer your own camera driver?
please refer to developer guide, Sensor Software Driver Programming to review your camera driver.

Thank you for your reply.
When I was testing without a connected camera, this was a normal error. I don’t need to fix this bug. In dmesg.txt, kernel panic is caused by these two errors. Is there a way to solve the kernel panic problem?

hello Seven0,

you should configure the DT settings to disable cameras if you don’t need camera service.
anyways, please help me understand your real use-case. or, what’s the actual test pipeline you’re running with.

There were a lot of errors when the camera started up and in this case we tested the stability of the system. The error was caused by a defect in our hardware. The problem now is that after connecting the camera and starting the camera, although there are many errors, it does not cause a kernel panic. If you unplug the camera at this point, the kernel will panic after a few minutes, causing the system to restart. We don’t want the system to reboot.
dmesg.txt is log
dmesg.txt (123.9 KB)
Thanks.

hello Seven0,

I still need to confirm what’s the real use-case.
for instance, is it intended to disconnected the camera abruptly?

During autopilot, the camera connection may become loose, causing the camera connection to disconnect. Manually disconnect the camera to simulate this phenomenon

hello Seven0,

may I know which test app you’re used? FYI, argus_camera application does not have a mechanism to automatically stop on detecting errors currently.
you have to execute application with error handling mechanism, such as… userAutoExposure.
please see-also similar discussion thread for reference, i.e. Topic 243051.

#! /bin/bash

export DISPLAY=:0

###v4l2src plugin

gst-launch-1.0 v4l2src device=/dev/video0 ! ‘video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)30/1’ !
nvvidconv ! ‘video/x-raw(memory:NVMM), width=(int)480, height=(int)270, format=(string)NV12, framerate=(fraction)30/1’ !
nv3dsink window-x=0 window-y=0
v4l2src device=/dev/video1 ! ‘video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)30/1’ !
nvvidconv ! ‘video/x-raw(memory:NVMM), width=(int)480, height=(int)270, format=(string)NV12, framerate=(fraction)30/1’ !
nv3dsink window-x=480 window-y=0
v4l2src device=/dev/video2 ! ‘video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)30/1’ !
nvvidconv ! ‘video/x-raw(memory:NVMM), width=(int)480, height=(int)270, format=(string)NV12, framerate=(fraction)30/1’ !
nv3dsink window-x=960 window-y=0
v4l2src device=/dev/video3 ! ‘video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)30/1’ !
nvvidconv ! ‘video/x-raw(memory:NVMM), width=(int)480, height=(int)270, format=(string)NV12, framerate=(fraction)30/1’ !
nv3dsink window-x=1440 window-y=0
v4l2src device=/dev/video4 ! ‘video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)30/1’ !
nvvidconv ! ‘video/x-raw(memory:NVMM), width=(int)480, height=(int)270, format=(string)NV12, framerate=(fraction)30/1’ !
nv3dsink window-x=0 window-y=270
v4l2src device=/dev/video5 ! ‘video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)30/1’ !
nvvidconv ! ‘video/x-raw(memory:NVMM), width=(int)480, height=(int)270, format=(string)NV12, framerate=(fraction)30/1’ !
nv3dsink window-x=480 window-y=270
v4l2src device=/dev/video6 ! ‘video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)30/1’ !
nvvidconv ! ‘video/x-raw(memory:NVMM), width=(int)480, height=(int)270, format=(string)NV12, framerate=(fraction)30/1’ !
nv3dsink window-x=960 window-y=270
v4l2src device=/dev/video7 ! ‘video/x-raw, width=(int)1920, height=(int)1080, framerate=(fraction)30/1’ !
nvvidconv ! ‘video/x-raw(memory:NVMM), width=(int)480, height=(int)270, format=(string)NV12, framerate=(fraction)30/1’ !
nv3dsink window-x=1440 window-y=270 -ev
Using this script to preview the camera and then disconnect the camera will cause panic

hello Seven0,

since it’s v4l2src plugin, it’s VI driver to handle the corruption.
could you please add -e flag into gst pipeline, which sending an EoS when stream termination, gather another kernel logs for reference.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.