Matthew

[boot.log](https://github.com/ccrisan/motioneyeos/files/6528373/boot.log) [dmesg.log](https://github.com/ccrisan/motioneyeos/files/6528374/dmesg.log) [messages.log](https://github.com/ccrisan/motioneyeos/files/6528375/messages.log) [motion.log](https://github.com/ccrisan/motioneyeos/files/6528376/motion.log) [motioneye.log](https://github.com/ccrisan/motioneyeos/files/6528377/motioneye.log) The reboots seem graceful I think due to firmware issue: > 2021-05-23 15:45:54: [motioneye] ERROR: could not terminate the motion process > 2021-05-23 15:45:54: [motioneye]...

``` [root@MotionEye ~]# uptime 17:33:55 up 1:09, load average: 4.30, 4.31, 4.27 [root@MotionEye ~]# vcgencmd measure_temp temp=55.0'C [root@MotionEye ~]# vcgencmd get_throttled throttled=0x0 ``` Performance is obviously not great without hardware...

Linking in https://github.com/ccrisan/motioneyeos/issues/2043 and https://github.com/ccrisan/motioneyeos/issues/2510 Do you use Raspberry Pi 4? I originally built the SD card for my 8GB Pi4 (hence the dev build).. the Pi Zero has been...

``` [root@MotionEye log]# uptime 18:44:38 up 5:36, load average: 1.86, 2.13, 2.33 [root@MotionEye log]# vcgencmd measure_temp temp=51.0'C [root@MotionEye log]# vcgencmd get_throttled throttled=0x0 ``` I'm going to try replacing files in...

I have made a frankenstein motionEyeOS boot partition (FAT, so easily done in Windows): * I deleted fixup.dat and start.elf (firmware files transferred to the VideoCore GPU prior to booting)....

System much more responsive and performant generally (even things like booting before I even switched back to OMX).. Am still observing motion locking up on some resolutions as per https://github.com/Motion-Project/motion/issues/433...

Have a better test bed: ``` /etc/init.d/S85motioneye stop ffmpeg -f video4linux2 -video_size 800x600 -framerate 25 -i /dev/video0 -codec:v h264_omx -y -f h264 /dev/null ffmpeg -f video4linux2 -video_size 1024x768 -framerate 25...

Looks like rebooting inbetween testing and 1024x768 runs fine.. suspect it is triggered at certain resolutions/bitrates Now trying to see if I can get ffmpeg to use random data as...

Reproduced on Raspberry Pi 3b with fresh Raspberry Pi OS Lite install (and update and dist-upgrade). `ffmpeg -f video4linux2 -video_size 1024x768 -framerate 25 -i /dev/video0 -codec:v h264_omx -y -f h264...

Have compiled ffmpeg from source. Same issue. Concluding that the problem is ffmpeg and/or the driver (drivers/media/common/videobuf2/videobuf2-core.c) not sanity checking ffmpeg input. Not a Motion/MotionEye/MotionEyeOS/RPI3/RPI4 specific issue. ``` root@test:~/ffmpeg# ./ffmpeg...