Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

bcm2835-codec: encoder stops working after some time

Abierto
  • ¿Algo no está bien?
#7,675 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
32/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
c, linux
Área
embedded-iot

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
C
Estrellas
13.2k
Forks
5.5k
Merge medio
2 d 9 h
PR fusionados (30 d)
21

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de raspberrypi/linux

Todos los issues de raspberrypi/linux

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.