Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 7521

Interfacing (DSI, CSI, I2C, etc.) • Re: Experiencing system freeze during long streaming tests

$
0
0
Hi all,
I've been facing system freeze issue when I subject my camera to long streaming tests. It's a Pi 5 kit running Debian 12 Bookworm OS.
The error logs are as follows:

Code:

[26466.254279] vc4-drm axi:gpu: [drm] *ERROR* [CRTC:92:crtc-2] cleanup_done timed out[26466.254304] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000148[26466.263146] Mem abort info:[26466.265943]   ESR = 0x0000000096000005[26466.269706]   EC = 0x25: DABT (current EL), IL = 32 bits[26466.275039]   SET = 0, FnV = 0[26466.278281]   EA = 0, S1PTW = 0[26466.282187]   FSC = 0x05: level 1 translation fault[26466.287110] Data abort info:[26466.289997]   ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000[26466.295510]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0[26466.300581]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0[26466.305934] user pgtable: 16k pages, 47-bit VAs, pgdp=0000000003398000[26466.312558] [0000000000000148] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000[26466.321350] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP[26466.327642] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device algif_hash algif_skcipher af_alg bnep brcmfmac_wcc vc4 binfmt_misc brcmfmac brcmutil snd_soc_hdmi_codec imx290 drm_display_helper v4l2_cci regmap_i2c cec cfg80211 rpi_hevc_dec drm_dma_helper snd_soc_core v4l2_mem2mem rp1_cfe pisp_be v3d snd_compress v4l2_fwnode v4l2_async videobuf2_dma_contig snd_pcm_dmaengine videobuf2_memops snd_pcm gpu_sched videobuf2_v4l2 snd_timer videodev drm_shmem_helper snd drm_kms_helper rp1_mailbox i2c_designware_platform videobuf2_common rp1_pio mc i2c_designware_core rp1_adc spidev joydev hci_uart btbcm bluetooth aes_ce_blk aes_ce_cipher ghash_ce gf128mul sha2_ce sha256_arm64 sha1_ce ecdh_generic ecc rfkill libaes sha1_generic raspberrypi_hwmon i2c_brcmstb raspberrypi_gpiomem spi_bcm2835 rp1_fw gpio_keys nvmem_rmem uio_pdrv_genirq uio i2c_dev drm ledtrig_pattern drm_panel_orientation_quirks fuse backlight dm_mod ip_tables x_tables ipv6[26466.412233] CPU: 0 UID: 1000 PID: 952 Comm: labwc Not tainted 6.12.41-v8-16k+ #3[26466.419656] Hardware name: Raspberry Pi 5 Model B Rev 1.1 (DT)[26466.425506] pstate: 00400009 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)[26466.432493] pc : drm_atomic_helper_setup_commit+0x2ec/0x7f8 [drm_kms_helper][26466.439586] lr : drm_atomic_helper_setup_commit+0x2c8/0x7f8 [drm_kms_helper][26466.446671] sp : ffffc00083d7ba60[26466.449990] x29: ffffc00083d7ba60 x28: ffff8000034f1800 x27: 0000000000000004[26466.457152] x26: ffff80000335ce00 x25: 0000000000000028 x24: ffff80000adae000[26466.464313] x23: 0000000000000000 x22: ffffd06fcf6103e8 x21: ffff800009be9d80[26466.471475] x20: ffffd06fcda753c0 x19: ffff800201c4c5c0 x18: ffffffffffffffff[26466.478636] x17: 6d697420656e6f64 x16: 5f70756e61656c63 x15: 205d322d63747263[26466.485797] x14: 3a32393a43545243 x13: 74756f2064656d69 x12: 7420656e6f645f70[26466.492958] x11: 756e61656c63205d x10: ffffd06fcfce04e8 x9 : ffffd06fce505410[26466.500119] x8 : 00000000ffffefff x7 : ffffd06fcfce04e8 x6 : 0000000000000000[26466.507280] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000004[26466.514441] x2 : 0000000000000038 x1 : ffff80000325b400 x0 : 0000000000000000[26466.521602] Call trace:[26466.524049]  drm_atomic_helper_setup_commit+0x2ec/0x7f8 [drm_kms_helper][26466.530784]  drm_atomic_helper_commit+0x60/0x190 [drm_kms_helper][26466.536909]  drm_atomic_nonblocking_commit+0x64/0x80 [drm][26466.542460]  drm_mode_atomic_ioctl+0x6a8/0xcd8 [drm][26466.547468]  drm_ioctl_kernel+0xc0/0x140 [drm][26466.551955]  drm_ioctl+0x210/0x4e8 [drm][26466.555915]  __arm64_sys_ioctl+0xb0/0x100[26466.559938]  invoke_syscall+0x50/0x120[26466.563696]  el0_svc_common.constprop.0+0x48/0xf8[26466.568414]  do_el0_svc+0x28/0x40[26466.571734]  el0_svc+0x30/0x100[26466.574881]  el0t_64_sync_handler+0x13c/0x158[26466.579248]  el0t_64_sync+0x190/0x198[26466.582918] Code: 52800702 f94012a1 9ba20400 f9400c00 (f940a413) [26466.589032] ---[ end trace 0000000000000000 ]---
The camera is seen to be actively dumping frames out when probed with an oscilloscope. I'm also able to ping to the Pi from another device and also able to take remote access through ssh as well. But I cannot interact with the Pi directly
What can be done about this issue?

Hi all,
Some additional context:

OS version using "cat /etc/debian_version" : 12.10
Version in boot splash logo : Release 5.6 - April 2025
Kernel code base : https://github.com/raspberrypi/linux/tree/rpi-6.12.y (commit ac69f097e1fba94502cbd36278db204120a37943)

The long stream test is done with two IMX462 cameras (using the IMX290 driver merged in the kernel source) as well as with two IMX662 cameras (with a driver based on IMX290 driver). Simultaneous streaming is done at 10 bit bayer format, 1920x1080p, 30fps each.

The command I used is as follows:
libcamera-vid --mode 1920:1080:10:U --width 1920 --height 1080 -t 0 -f --camera <id> --tuning-file=<tuning-file-path>

The system freeze is observed anywhere between 30 mins to 15 hours after the test commences. On rare occasions I'm able to ping as well as take remote access to the Pi while it's in a frozen state.

The drive link contains some of the kernel logs observed.
https://drive.google.com/drive/folders/ ... sp=sharing

Statistics: Posted by ashwin0711 — Wed Oct 22, 2025 4:14 am



Viewing all articles
Browse latest Browse all 7521

Trending Articles