ssh in (eg with Putty on windows or ssh on Linux then enter the following command:
This will produce kodi stacktraces, upload it to ix.io and output the URL of the uploaded backtrace (eg http://ix.io/4GFw)
so long,
Hias
ssh in (eg with Putty on windows or ssh on Linux then enter the following command:
This will produce kodi stacktraces, upload it to ix.io and output the URL of the uploaded backtrace (eg http://ix.io/4GFw)
so long,
Hias
Might be worth testing with a clean kodi installation without addons.
See here: RE: possible memory leak in nightly builds
so long,
Hias
This seems to be a bug in inputstream.adaptive, probably this one https://github.com/xbmc/inputstream.adaptive/issues/1362
No solution yet, we have to wait until i.a is fixed.
so long,
Hias
The last line in the kodi log is from the jellyfin addon. Try disabling that and see if that improves things.
BTW: you seem to have quite a lot of addons, scripts and skins installed. It might be worth disabling them one by one (or start with a clean kodi and install addons one after the other). ISTR script.embuary.helper has caused crashes in the past and there are also error log messages from script.lazytv.
so long,
Hias
hmm, according to the logs mmcblk0 should be a 128GB SD card. However the storage partition seems to contain only a 1GB filesystem - that should have been about 127GB instead. 1GB isn't enough for kodi plus addons...
so long,
Hias
You can either use 11.0.1 and wait for 11.0.4 (no ETA on it though yet) or install the latest LE11 test build from here: https://test.libreelec.tv/11.0/RPi/RPi4/
The official 11.0.3 version has not been changed.
so long,
Hias
Drop the "=1" after systemd.debug_shell (that would set the serial device), console=serial0,115200 systemd.debug_shell is working fine here.
I also have dtoverlay=disable-bt here in config.txt so that the AMA0 UART is used for the console.
so long,
Hias
Yes, that repo is certainly banned and you might have got other crap from it that's not flagged by kodi's pastebin site / banned list.
As we don't know if it's the banned crap, some other addon, or kodi (latter is not too likely since I don't see the issue here) you need to do a clean install anyway to narrow it down. Start with clean LE kodi, add one addon after the other and see if things change.
so long,
Hias
Can confirm that the memory leak is still present.
You might want to start by doing a clean installation without any of the banned repositories/addons https://kodi.wiki/view/Official:Forum_rules/Banned_add-ons
If the problem persists post a new log, until then support for your setup is suspended.
so long,
Hias
I'm not seeing this here:
Time arm core Core Temp (Max) IRQ/s RX B/s TX B/s %user %nice %sys+ %total MemFreeKB / %used
======== ======= ======= =============== ====== =========== =========== ====== ====== ====== ====== =================
16:38:15 700Mhz 256Mhz 48.20C (48.20C) 613 189 371 1.99 0.00 0.62 2.98 3,653,008 / 5.5%
16:38:17 700Mhz 256Mhz 47.71C (48.20C) 619 32 126 1.99 0.12 0.50 2.96 3,653,008 / 5.5%
16:38:19 700Mhz 256Mhz 47.23C (48.20C) 634 32 126 1.99 0.12 0.74 2.95 3,653,008 / 5.5%
16:38:21 700Mhz 256Mhz 48.20C (48.20C) 645 32 126 2.23 0.12 0.62 2.95 3,653,008 / 5.5%
16:38:23 700Mhz 256Mhz 48.20C (48.20C) 608 32 126 2.11 0.12 0.50 2.96 3,653,008 / 5.5%
16:38:25 700Mhz 256Mhz 48.69C (48.69C) 610 32 126 1.99 0.12 0.37 2.94 3,653,008 / 5.5%
16:38:27 700Mhz 256Mhz 48.20C (48.69C) 629 32 126 2.23 0.25 0.37 2.96 3,653,008 / 5.5%
16:38:29 700Mhz 256Mhz 47.71C (48.69C) 654 94 126 2.11 0.12 0.37 3.08 3,653,008 / 5.5%
16:38:31 700Mhz 256Mhz 47.23C (48.69C) 622 139 126 2.11 0.25 0.50 2.95 3,653,008 / 5.5%
16:38:33 700Mhz 256Mhz 48.20C (48.69C) 616 246 126 2.11 0.12 0.50 2.83 3,653,008 / 5.5%
16:38:35 700Mhz 256Mhz 48.20C (48.69C) 1,408 3,773 2,854 2.73 0.12 1.49 4.69 3,653,028 / 5.5%
16:38:37 700Mhz 256Mhz 47.71C (48.69C) 628 32 126 1.99 0.25 0.37 2.96 3,653,028 / 5.5%
16:38:39 700Mhz 256Mhz 47.71C (48.69C) 656 233 876 2.23 0.25 0.25 3.08 3,653,028 / 5.5%
16:38:41 700Mhz 256Mhz 48.69C (48.69C) 581 65 158 2.11 0.12 0.37 2.82 3,653,028 / 5.5%
16:38:43 700Mhz 256Mhz 49.17C (49.17C) 651 32 126 1.99 0.12 0.62 3.07 3,653,280 / 5.5%
16:38:45 700Mhz 256Mhz 48.20C (49.17C) 654 183 313 2.23 0.12 0.50 2.96 3,653,280 / 5.5%
16:38:47 700Mhz 256Mhz 48.20C (49.17C) 634 32 126 2.23 0.12 0.50 2.94 3,653,028 / 5.5%
16:38:49 700Mhz 256Mhz 49.17C (49.17C) 576 32 126 2.11 0.25 0.12 2.95 3,653,028 / 5.5%
16:38:51 700Mhz 256Mhz 47.71C (49.17C) 638 32 126 2.11 0.12 0.50 2.94 3,653,028 / 5.5%
16:38:53 700Mhz 256Mhz 47.71C (49.17C) 638 32 126 2.11 0.12 0.50 3.08 3,653,028 / 5.5%
16:38:55 700Mhz 256Mhz 48.69C (49.17C) 641 32 126 2.23 0.25 0.50 2.85 3,653,028 / 5.5%
16:38:58 700Mhz 256Mhz 49.17C (49.17C) 585 32 126 2.11 0.12 0.25 2.94 3,653,028 / 5.5%
16:39:00 700Mhz 256Mhz 48.69C (49.17C) 647 63 126 2.23 0.12 0.62 3.10 3,653,028 / 5.5%
16:39:02 700Mhz 256Mhz 48.69C (49.17C) 715 364 456 2.23 0.12 0.74 3.08 3,653,028 / 5.5%
16:39:04 700Mhz 256Mhz 47.23C (49.17C) 647 32 126 2.11 0.12 0.50 2.97 3,653,028 / 5.5%
16:39:06 700Mhz 256Mhz 48.69C (49.17C) 576 62 146 2.11 0.12 0.50 2.96 3,653,028 / 5.5%
16:39:08 700Mhz 256Mhz 47.71C (49.17C) 640 32 126 1.86 0.12 0.62 2.95 3,653,028 / 5.5%
16:39:10 700Mhz 256Mhz 49.66C (49.66C) 646 32 126 2.23 0.12 0.37 2.96 3,653,028 / 5.5%
16:39:12 700Mhz 256Mhz 48.20C (49.66C) 648 32 126 2.11 0.12 0.87 2.95 3,653,028 / 5.5%^C
Display More
What were you (or kodi doing) at that time?
so long,
Hias
Whatever. You have your theory and I tried to explain some more details. Anyways I'm out of this thread.
so long,
Hias
Under the hood JACK is using ALSA (as that's the only way to access audio devices in Linux). So adding JACK to the chain is at best a workaround for some kodi bug.
so long,
Hias
If kodi is crashing on other Linux systems, too, then it'd be best to report it to kodi devs here: https://github.com/xbmc/xbmc/issues - this sounds like it might be a kodi bug.
so long,
Hias
Do you have the AVR connected to SPDIF out on the TV?
The log looks fine, kodi is properly signalling PCM and passthrough to the hdmi driver.
So this likely is an issue with your TV's SPDIF out, AVR's SPDIF in or some combination of both. Check if your TV has some settings to control SPDIF out.
so long,
Hias
Do a clean install without your piracy crap addons - that stuff is not supported here.
so long,
Hias
Thanks for testing, I've PR'ed the workaround/fix https://github.com/LibreELEC/LibreELEC.tv/pull/8126
Concerning your other SPDIF/passthrough issue: please open a separate bug report thread for that and provide a full debug log (using pastekodi or the log file upload function in LE settings)
so long,
Hias
hbbs can you please test and report back if this build works?
https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi2.arm-12.0-devel-20230908210215-01c68ef.tar
so long,
Hias
hbbs thanks, I've managed to reproduce this issue locally now and will investigate it. ATM we don't need anything else from you
so long,
Hias