Posts by mglae

    It looks like video=HDMI-A-1:D is now in the command line, so I will leave it running today/overnight to see how it goes (unless there's anything else?).

    Good plan.

    I don't want to frighten you, but:

    1. [ 0.669046] WARNING: CPU: 2 PID: 1 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:1648 core_link_enable_stream+0xcc1/0x10cb

    dc_link.c:1648 is inside HDMI configuration and may be related to the crash.

    To my surprise video=HDMI-A-1:D is missing in your kernel command line.

    This is a known bug that seems to be forgotten to merge.

    1) Remove your current configuration

    1. getedid delete

    and reboot.

    2) Get the fixed script

    1. cd
    2. wget
    3. chmod +x getedid

    3) Create the new configuration

    1. /storage/getedid create

    4) Reboot and post dmesg|paste again.

    1) Just to be sure: did you reboot after creating the custom EDID?

    2) Insert

    1. <loglevel hide="false">1</loglevel>
    2. <debug>
    3. <showloginfo>false</showloginfo>
    4. </debug>

    into your advancedsettings.xml and restart kodi to have debug logging without overlay.

    3) Please log in via ssh, type dmesg|paste and post the resulting URL here.

    You can safely delete the core files:

    1. find /storage/.cache/cores/ -type f -delete

    But most likely the failtng process continues crashing and generating core files. Keep an eye on the folder and post the output of ls -l /storage/.cache/cores when new files arrive.

    LibreELECs du command is using a block size of 512 bytes by default.

    Time to exchange your SD card.

    3181944kB kodi.bin RSS size in 4141 seconds (from dmesg) is unlikely for the found slow growing memory leak.

    In the crash log there are a lot of

    1. 2019-06-15 21:10:02.489 T:139781078423296 NOTICE: VAAPI::Close
    2. 2019-06-15 21:10:02.489 T:139780029404928 NOTICE: COutput::OnExit: Output Thread terminated
    3. 2019-06-15 21:10:02.494 T:139780029404928 NOTICE: COutput::OnStartup: Output Thread created

    at the end before crashing in

    1. Thread 1 (Thread 0x7f2151869700 (LWP 976)):
    2. #0 0x00007f2168678661 in vaDestroyContext () from /usr/lib/
    3. #1 0x00007f216781bf0c in ?? () from /usr/lib/
    4. #2 0x00007f216745a88a in ?? () from /usr/lib/
    5. #3 0x00007f216753c705 in ?? () from /usr/lib/
    6. #4 0x00007f216753d551 in ?? () from /usr/lib/
    7. [...]

    Looks like "something" fails an then run out of resources. ;-)

    Updated mesa and/or kernel driver may help on your hardware but there is no guaranty.