A kernel panic by the camera driver

Hi, nvidia teams:
There is a kernel panic by camera driver. the log says that “capture control message timed out” and “vi_capture_release: release channel IVC failed”, so what error will cause this happen? the error is as follow and I have uploaded the kernel log:
<3>[24288.363397] INFO: task sync:2179178 blocked for more than 120 seconds.
<3>[24288.370160] Tainted: G W OE 5.10.104-tegra #1
<3>[24288.376288] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
<6>[24288.384419] task:sync state:D stack: 0 pid:2179178 ppid:2177893 flags:0x00000008
<6>[24288.384429] Call trace:
<6>[24288.384445] __switch_to+0xc8/0x120
<6>[24288.384457] __schedule+0x3d0/0x910
<6>[24288.384462] schedule+0x74/0x100
<6>[24288.384469] wb_wait_for_completion+0x84/0xb0
<6>[24288.384473] sync_inodes_sb+0xb8/0x230
<6>[24288.384478] sync_inodes_one_sb+0x34/0x40
<6>[24288.384485] iterate_supers+0xa8/0x140
<6>[24288.384490] ksys_sync+0x4c/0xc0
<6>[24288.384495] __arm64_sys_sync+0x14/0x20
<6>[24288.384501] el0_svc_common.constprop.0+0x7c/0x1c0
<6>[24288.384506] do_el0_svc+0x34/0xa0
<6>[24288.384511] el0_svc+0x1c/0x30
<6>[24288.384516] el0_sync_handler+0xa8/0xb0
<6>[24288.384520] el0_sync+0x16c/0x180
<6>[24838.185249] usb 1-3: USB disconnect, device number 2
<3>[24840.801532] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
<3>[24840.801540] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
<4>[24840.811143] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
<3>[24840.819888] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
<4>[24840.829835] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
<4>[24840.839408] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
<3>[24841.857507] tegra194-vi5 13e40000.host1x:vi0@15c00000: capture control message timed out
<3>[24841.857510] tegra194-vi5 13e40000.host1x:vi0@15c00000: capture control message timed out
<3>[24841.857515] tegra194-vi5 13e40000.host1x:vi0@15c00000: vi_capture_release: release channel IVC failed
<3>[24841.865859] tegra194-vi5 13e40000.host1x:vi0@15c00000: vi_capture_release: release channel IVC failed
<6>[24841.865873] ------------[ cut here ]------------
<6>[24841.874366] ------------[ cut here ]------------
dmesg-ramoops-0 (106.6 KB)

hello 261136636,

may I know which camera module you’re using?
please refer to Applications Using V4L2 IOCTL Directly by use V4L2 IOCTL to verify basic camera functionality.

BTW,
which JetPack release version you’re now used?

Hi, JerryChang:
1.We use sensing camera module, the product link is follow:
https://www.sensing-world.com/productinfo/1975302.html
2.The jetpack version we used is “jetpack GA”

In this issue, Our program are only continuous capturing picture from “video 0”, “video 1”, “video 2”,
but on the time " [24840.801532]", vi capture failed from these three channels and cause
kernel panic.

hello 261136636,

please check release tag for L4T version. $ cat /etc/nv_tegra_release
there’s by default support dual imx390 with SerDes chips.
for example, $public_sources/kernel_src/hardware/nvidia/platform/t23x/concord/kernel-dts/cvb/tegra234-p3737-0000-camera-imx390-a00.dtsi

so… had you update the device tree from sensor vendor? please also contact with them to confirm the workable release verison.

Hi,JerryChang:
1.the version is:

R35 (release), REVISION: 1.0, GCID: 31250864, BOARD: t186ref, EABI: aarch64, DATE: Thu Aug 11 03:40:29 UTC 2022

2.We have confirm the device tree with the sensor vendor.

hello 261136636,

so… may I know the sensor vendor is?
has this camera module valid by any JetPack release version?

Hi,JerryChang:
This module is a sensing camera module, the product link is:
https://www.sensing-world.com/productinfo/1975302.html
It use imx390 sensor.

This module can work well in “jetpack GA” and “jetpack 5.0.1”.
This bug do not apper every time. it only appered once.
This bug is a stability issue, not a function issue.

hello 261136636,

thanks for explanation, could you please share the failure rate for reference.

furthermore,
since the latest Jetpack release is now JetPack-5.1.1/l4t-r35.3.1, is it possible for moving to the latest Jetpack release for confirmation.

Hi,JerryChang:
Till now , it appered only once.
We will update jetpack version to “JetPack-5.1.1”, and see if it appered in "JetPack-5.1.1.

hello 261136636,

please update Jetpack version to JP-5.1.1/l4t-r35.3.1,
please share the complete reproduce steps, and error messages if you’re able to see such kernel panic again.

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