Kodi Segmentation Fault error

notthesame

@Rascas Kodi 18.6 or 7 acted funny with this, exiting or playing music did some crazy music playback also some things like ogv files not working, idk I haven't asked theses cos we got updated I think we have a new update and hopefully nothing broken.

Do you happen to know why ogv files basicly theirs not working?, I get a crash black screen then restarts I have the log but I need to upload to report this.

Rascas

@notthesame ogg, flac, mp3... all works fine. No log, no problem.

notthesame

@Rascas https://pastebin.com/NKKrUPfj
here my crash log ogv? not sure whats up, maybe i miss something and this is a new image thanks.

domb84

@Rascas I'll reproduce and get some debug logs over!

domb84

My installation got completely destroyed with a kernel update that corrupted the boot partition for some reason. Since then, I've re-imaged the SD card again, updated all RetroPie packages and made sure not to update and kernel packages.

Installed kodi through the retropie packages which is 18.7 I believe. This is now working without issue!

There is an update to kodi available, perhaps the CEC issue is introduced with 18.8? Or maybe a kernel issue.

domb84

@Rascas @domb84 Update... have started getting random segfaults again on exit so I spoke to soon. Logs attached.

https://mega.nz/file/oaBziCjQ#y7sPw8C-Vk4MjeMRaXM4KBbfegReKX7DGjyrr3TKNLY

domb84

@domb84 the following settings in /boot/config.txt have fixed my segmentation fault, i'm unsure why, but doing some reading shows that when using dtoverlay=vc4-fkms-v3d, the max_framebuffers should match the number of displays. I believe this might be the issue given the problems with CEC on the second display?

https://www.raspberrypi.org/forums/viewtopic.php?t=245789

max_framebuffers=1
hdmi_enable_4kp60=1
gpu_mem=512 (i know this is higher than it should / needs to be, was just testing)
hdmi_ignore_cec_init=1
hdmi_force_hotplug=1

My last remaining issue is that quiting Kodi usually results in a blank screen. For some reason it picks a new display format. Switching the display to another input and back again resolves that.

domb84

@domb84 forcing boot resolution to 720p60 resolves the black screen issue in retropie, kodi will still switch to 4k60 when configured. exiting to retropie will switch back to 720p60. Also has the added benefit of resolving the slowness in redream at 4k, and overriding the resolution has no effect. overclocking also has no negative effect on cec or emulation.

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
# reduce max_framebuffers to 1 to match displays
max_framebuffers=1
[all]
#dtoverlay=vc4-fkms-v3d
#overscan_scale=1
# 4k60 support for kodi
hdmi_enable_4kp60=1
gpu_mem=320
hdmi_ignore_cec_init=1
hdmi_force_hotplug=0
# force boot and emulationstation to 720p
hdmi_group=1
hdmi_mode=4
# overclocking
over_voltage=6
arm_freq=2100
gpu_freq=750

Rascas

@domb84 Looking at your crashlogs, it indicates a CEC relative problem. But that doesn't mean it is really a CEC library problem, it can be other things. For example, I recommend that you try a different HDMI cable, one 2.0 preferably not a long one. I don't believe that max_framebuffers would cause a problem as I and most use the default settings.
And also if you get corrupted files, I also would check the SD card. Updating the kernel shouldn't destroy your installation. I also had similar problems in the past with Samsung EVO sdcards. Although most of the things worked fine, if I did heavy read/writes to sdcard, for example, updating Raspbian packages or downloading torrents I got corrupted filesystem. My only solution was just using another SD card from a different brand and the problems stopped.

domb84

@Rascas the issue is max_framebuffers=2 on retropie. It should be max_framebuffers=1 when using a single display. This resolved my issue.
Tried all different cables, monitor inputs, monitor outputs, rebuilding libcec. only solution was max_framebuffers=1.

Thread here shows it should be set to match your displays. https://www.raspberrypi.org/forums/viewtopic.php?t=245789

I'll accept maybe it's an oddity with my display, but since making that change i've been unable to reproduce it.

Think the corruption was perhaps bad luck... but I've seen a few reports of recent kernel/raspbian updates causing this.