Yeah, I’ve noticed the under-voltage messages. I think they mostly stop once the system is booted, and I doubt they’d cause a segfault, but I don’t know for sure what is causing it so… yes. Maybe.
FWIW I managed to get a core dump from kodi and had a look at it with gdb:
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Core was generated by `/usr/lib/kodi/kodi.bin'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x75fd198c in sc_reduce () from /usr/osmc/lib/libshairplay.so.0
[Current thread is 1 (Thread 0x722b3040 (LWP 21976))]
#0 0x75fd198c in sc_reduce () at /usr/osmc/lib/libshairplay.so.0
#1 0x08d7e05c in ()
I’m not sure how useful that is.
I’ve also run kodi through strace, and noted that we see a log message saying the webserver has started on port 80, a syscall reading from /dev/urandom and then the segfault happens.
I still get under voltage with all of the peripherals plugged in, but it seems only during boot. Afterwards, everything else seems to work fine (tvheadend, minidlna, and I see no problems when ssh’ed in).
To eliminate the under voltage as a cause, I’ve booted with nothing plugged into USB.
No under voltage this time, but still the same mediacenter segmentation fault and sad face loop.