bcm2835-codec: encoder stops working after some time
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 32/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- c, linux
- 领域
- embedded-iot
调研方向
Start from the dmesg strings: locate bcm2835_mmal_vchiq: timed out waiting for sync completion and vchiq_mmal_component_init: failed to create component in the MMAL/VCHIQ driver code, plus bcm2835_codec_create_component and bcm2835_codec_stop_streaming in the bcm2835-codec media driver. Trace how the sync-completion timeout leaves GPU-side resources or component handles unreleased across repeated start/stop cycles, and check error-path cleanup around -62 (ETIMEIMEOUT) failures. Done means identifying the leak or stuck state on repeated start/stop of ril.video_encode/ril.image_encode and confirming a reproduction path; the issue itself states reproduction is unknown, so this is maintainer-level kernel debugging rather than a startable first fix.
由索引模型根据 Issue 内容生成。
描述
Describe the bug
PiKVM users report that sometimes after several restarts and successful operation sessions, JPEG encoder (image_encode) and H.264 (video_encode) stop initializing. It seems this is a bit similar to #7163
Dmesg:
[17056.541287] bcm2835_mmal_vchiq: timed out waiting for sync completion
[17056.547944] bcm2835-codec bcm2835-codec: bcm2835_codec_stop_streaming: Failed disabling i/p port, ret -62
[17059.613354] bcm2835_mmal_vchiq: timed out waiting for sync completion
[17059.619987] bcm2835-codec bcm2835-codec: bcm2835_codec_stop_streaming: Failed enabling component, ret -62
[17062.685429] bcm2835_mmal_vchiq: timed out waiting for sync completion
[17065.757505] bcm2835_mmal_vchiq: timed out waiting for sync completion
[94500.799477] bcm2835_mmal_vchiq: timed out waiting for sync completion
[94500.806073] bcm2835_mmal_vchiq: vchiq_mmal_component_init: failed to create component -62 (Not enough GPU mem?)
[94500.816710] bcm2835-codec bcm2835-codec: bcm2835_codec_create_component: failed to create component ril.video_encode
[108339.129068] bcm2835_mmal_vchiq: timed out waiting for sync completion
[108339.135924] bcm2835_mmal_vchiq: vchiq_mmal_component_init: failed to create component -62 (Not enough GPU mem?)
[108339.147743] bcm2835-codec bcm2835-codec: bcm2835_codec_create_component: failed to create component ril.video_encode
[108350.649267] bcm2835_mmal_vchiq: timed out waiting for sync completion
[108350.656703] bcm2835_mmal_vchiq: vchiq_mmal_component_init: failed to create component -62 (Not enough GPU mem?)
[108350.667764] bcm2835-codec bcm2835-codec: bcm2835_codec_create_component: failed to create component ril.video_encode
[109034.436851] bcm2835_mmal_vchiq: timed out waiting for sync completion
[109034.444505] bcm2835_mmal_vchiq: vchiq_mmal_component_init: failed to create component -62 (Not enough GPU mem?)
[109034.455702] bcm2835-codec bcm2835-codec: bcm2835_codec_create_component: failed to create component ril.video_encode
And (another user):
18:29:31 bcm2835_mmal_vchiq: timed out waiting for sync completion
18:29:31 vchiq_mmal_component_init: failed to create component -62
18:29:31 bcm2835-codec: failed to create component ril.image_encode
Steps to reproduce the behaviour
The exact method for reproducing is unknown, but it is said that this happens after several restarts of the process that initializes the M2M codec. Just run, stop and run again any encoder like gstreamer to capture and encode stream from tc358743 to h264, several times.
I can ask users to perform special diagnostics or provide SSH.
Device (s)
Raspberry Pi CM4
System
- Arch Linux ARM
version 288930ab4712b99596f32732664aaaeb881ef1e0 (clean) (release) (start)- 6.12.105-2-rpi (built from 73b1c785241360882ab9f7fb0793e775c25db325)
Logs
[root@cobas-pure-box kvmd-webterm]# cat /boot/config.txt
# PiKVM
# See /boot/overlays/README for all available options
initramfs initramfs-linux.img followkernel
dtoverlay=cma,cma-192
hdmi_force_hotplug=1
gpu_mem=192
enable_uart=1
dtoverlay=disable-bt
# USB emulation
dtoverlay=dwc2,dr_mode=peripheral
# Video and audio
dtoverlay=tc358743,4lane=1
dtoverlay=tc358743-audio
# I2C (display)
dtparam=i2c_arm=on
# Clock
dtoverlay=i2c-rtc,pcf8563,wakeup-source
# Passthrough
dtoverlay=vc4-kms-v3d
disable_overscan=1
dtparam=ant2
[root@cobas-pure-box kvmd-webterm]# cat /boot/cmdline.txt
root=LABEL=PIROOT ro rootwait console=serial0,115200 console=tty1 fsck.repair=yes audit=0
Additional context
No response
- 主要语言
- C
- 星标
- 13.2k
- 派生
- 5.5k
- 平均合并
- 2 天 9 小时
- 30 天内合并 PR
- 21
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
raspberrypi/linux 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
raspberrypi/linux#7415 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace app未关闭
难度 2/5 1-3 小时 新手友好度 72/100
raspberrypi/linux#7399 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
raspberrypi/linux#7357 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
raspberrypi/linux#7054 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 32/100
raspberrypi/linux#7674 · 1 条评论 ·
维护者通常 1 天内回复
查看 raspberrypi/linux 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
libsdl-org/SDL#16464 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
backend
难度 2/5 1-3 小时 新手友好度 68/100
BasedHardware/omi#20940 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1 小时以内 新手友好度 70/100
维护者通常 1 天内回复