Posts by mglae

CvH I've already prepared and build tested the patch, "only" need to push the PR.

The required patch of post 4 is not included into kernel 5.10.

The needed authentication plugins are missing in the images. I've created a fix.

The advice did come from @fuzzard on github.

But why are you the only one seeing the crash? Can you try a fresh installation on a spare card?

What if you disable ws-discovery by changing advancedsettings.xml to

<advancedsettings version="1.0">

<loglevel hide="false">1</loglevel> 
<debug>
  <extralogging>true</extralogging>
  <setextraloglevel>8388608</setextraloglevel>
</debug>

<setting id="services.wsdiscovery">false</setting>
</advancedsettings> 

Please create a debug crash log with WS-Discovery component logging by creating:

<advancedsettings version="1.0">

<loglevel hide="false">1</loglevel> 
<debug>
  <extralogging>true</extralogging>
  <setextraloglevel>8388608</setextraloglevel>
</debug>

</advancedsettings>

jim_p

1. Wrong thread, intel != AMD

2. In Mesa 21.0.3 there is at least https://gitlab.freedesktop.org/mesa/mesa/-/issues/4605 for Kabini GPUs, no idea if RV620 is affected.

Edit: issue 4605 this is already fixed in 10.0.0 with a patch. Maybe you can do a search about RV620.

PS: That reminds me we need to update Mesa for LE 10.0.1

Looks like installed Bluetooth Audio Device Changer addon. If yes uninstall it.

If not post a complete log file via LibreELEC Settings or pastekodi

There is a failing and not failing log!?

Add set -x to the start of the script to see what is executed.

To log the PA status add pactl info;pactl list

Quote from ghtester

how to enable debug logs from console.

This is is how to enable verbose crash logs.

To enable kodi debug logging (without OSD) use

<?xml version="1.0" encoding="UTF-8" ?>
<advancedsettings>
  <loglevel>1</loglevel>
</advancedsettings>

Yes, please do it again (with *.tar or *.img.gz) and post a log file via LibreELEC Settings or pastekodi if still failing.

If still not expecting support please do

touch /storage/.config/debug.enhanced

and post new logs

The kodi-autostart.service does have the required dependencies.

Use journalctl -b -0 -u kodi-autostart to check for logged error messages and post your complete autostart.sh.

To list the open files and processes involved use

lsof|grep /path/to/mount/point/

The nightmare is that you do accept OOM situations.

For research reasons a core dump is generated by default if possible. This can be disabled by

echo 0 >/proc/sys/vm/oom_dump_tasks

Tame your tvheadend. It was terminated while occupying 3351196kB memory.

Change WantedBy=multi-user.target=nfs to WantedBy=multi-user.target

Log Files.