Login at Kodi Home

n0rd1k · 2019-02-18, 19:48

Hello everyone. This is mi problem, each video I want to play, no matter witch codec or source (pvr also) stucks, sometimes at the beginning of the reproduction, sometimes few minutes after, and second after that audio also stops. The kodi log says: CVideoPlayerAudio: Tongue

rocess - stream stalled and CPU goes to 100% and I have to restart kodi from command line. I start it from systemd service under X11. Mi machine is an Intel g3930, 4gb ram, Ubuntu Linux 18.04. I also have in my Lan an Odroid C2 with libreelec 9.0 that plays the same videos from NFS share (shared mysql) and there is no problem, everything ok. Here are my pastebins:
http://paste.ubuntu.com/p/vhTyP499nB/
http://paste.ubuntu.com/p/bsZchTjwNf/
http://paste.ubuntu.com/p/vHQtpGdwTp/
http://paste.ubuntu.com/p/drvjsCw8zD/
http://paste.ubuntu.com/p/tRhGnTdzzG/
http://paste.ubuntu.com/p/v2TdJVszCP/
http://paste.ubuntu.com/p/rg5G6HNTrt/

Can someone tell me what could went wrong? Thanks in advance.

**fritsch** · 2019-02-18, 20:27

What's that:

Quote:[114219.698967] r8169 0000:01:00.0 enp1s0: link down
[114226.265620] r8169 0000:01:00.0 enp1s0: link up
[114316.358202] r8169 0000:01:00.0 enp1s0: link down
[114319.492989] r8169 0000:01:00.0 enp1s0: link up
[617808.054998] r8169 0000:01:00.0 enp1s0: link down
[617814.543037] r8169 0000:01:00.0 enp1s0: link up
[617898.020169] r8169 0000:01:00.0 enp1s0: link down
[617901.155481] r8169 0000:01:00.0 enp1s0: link up

You unplugged it several times?

n0rd1k · 2019-02-19, 10:53

Emmm no... mayby the router or the ethernet adapter are doing strange things... That could affect?

**fritsch** · 2019-02-19, 13:38

Can you reproduce with local file playback, please?

n0rd1k · 2019-02-19, 22:55

Hi! The error is with local files. The ubuntu is a local server-nas, that shares the database and the content (by nfs) with the remote libreelec, that does path substitution. The remote libreelec works perfectly, even the content is taken from the nfs, but the ubuntu server is getting the error, thus the content is completele local to it.

cage · 2019-02-20, 19:21

I'm experiencing the exact same thing.

**fritsch** · 2019-02-20, 20:48

You also have the exact same logfile? With the exact same 4.15 kernel?

cage · 2019-02-20, 21:37

Yes.

**fritsch** · 2019-02-20, 23:23

Then post it and upgrade your kernel to 4.18 or something (provided by the HW update)

n0rd1k · 2019-02-22, 20:07

Well, I crossgraded to x64 (yeah! a very hard effort, but its a thing y had be done long time ago) and now it looks to work fine. Thanks!

**fritsch** · 2019-02-22, 20:36

(2019-02-22, 20:07)n0rd1k Wrote: Well, I crossgraded to x64 (yeah! a very hard effort, but its a thing y had be done long time ago) and now it looks to work fine. Thanks!

Really? No kidding?

n0rd1k · 2019-02-22, 21:35

Yes yes, just reinstalling almost packet by packet but it was worth the effort. I also took the opportunity to clean not used and obsolete packages. A complete day of work, my eyes hurt Laugh

. So it looks like that kernel (i386) is doing bad things, now everything just works as expected, thanks!

**fritsch** · 2019-02-22, 21:41

I don't think so. There is a race somewhere which is very unlikely to trigger.