[fritsch]

No idea - your logfiles might or might not tell. For the hdd, include df -h | pastebinit

[D-an-W]

Morning fritsch, can I ask if the builds in the v17_videoplayer_testing/ folder have the same special features relating to Chromebox's as the one in the v15_2_EGL/chromebox/ or would it require a specific Chromebox "v17" version building?

[fritsch]

Nope ... not needed. It was made to care for idiocy :-)

Some people (and a whole lot chromebox users) refuse to read the wiki, the howto this forum post and so on. Therefre I decided, together with MattDevo, that we make the chromebox edition more failsafe ... the only change is: Don't use lanczos3 scaling when input source is > 1080p and don't use it when output resolution is > 1080p ...

[sijones2010]

Hi fritsch,

debug log for you http://pastebin.com/9vTgAf7Y

any more info required?

[wsnipex]

Note for PPA users: builds are currently disabled until the AudioEngine rewrite is complete.

[D-an-W]

Nope ... not needed. It was made to care for idiocy :-)

Some people (and a whole lot chromebox users) refuse to read the wiki, the howto this forum post and so on. Therefre I decided, together with MattDevo, that we make the chromebox edition more failsafe ... the only change is: Don't use lanczos3 scaling when input source is > 1080p and don't use it when output resolution is > 1080p ...

Cheers fritsch, so as long as I don't use the Chromebox on my 4K TV or watch 4K content i'm good with the Wiki settings?

[fritsch]

Hi fritsch,

debug log for you http://pastebin.com/9vTgAf7Y

any more info required?

Nope - all fine. When now time comes back - currently we both are busy with the AE transition to support non IEC passthrough in the future - which should boost Android to a new level ... so you need to wait. Please post the Debug Log again every week if we should forget it :-) Thanks.

[fritsch]

Nope ... not needed. It was made to care for idiocy :-)

Some people (and a whole lot chromebox users) refuse to read the wiki, the howto this forum post and so on. Therefre I decided, together with MattDevo, that we make the chromebox edition more failsafe ... the only change is: Don't use lanczos3 scaling when input source is > 1080p and don't use it when output resolution is > 1080p ...

Cheers fritsch, so as long as I don't use the Chromebox on my 4K TV or watch 4K content i'm good with the Wiki settings?

Yeah. When something stutters when you e.g. downscale 4k content to 1080p output or if you run the chromebox at 4k@30 even on the gui (which you should highly avoid) - then you can manually turn off Lanczos3 optimized. As the chromebox is too slow to downscale 4k@60 to 1080p60 with lanczos3 and it is also too slow to upscale 1080p24 to 4k@p24 with this method.

[noggin]

I always use 'o' to check for drops, skips and other info just not sure when is sw/hw decoding in this case.
I've seen ffmpeg VAAPI so what about that one.
Hmmm maybe all that show VAAPI in dc: is hw decoded and there rest is sw?

If you see VAAPI then that means hardware decoding, if you don't see VAAPI then it's likely to be software. (My mistake if there is an ffmpeg-vaapi mode - that would be hardware acceleration still)

[fritsch]

There is a possible combination of: vaapi decoding + cpu copy + ffmpeg post processing - especially when yadif is used :-) ... if one sticks to the settings given in post 2 - that won't happen though.

[teki4u]

In your dmesg there I see a kodi segfault at the end - please also upload the crashlog which is in your home directory. Check temperatures, also do a complete memory test (!) of the box via memtest86+. Concerning sw decoding: If you press "o" - hw decoded always has "-vaapi" in the dc line, e.g. dc: ff-h264-vaapi

CRASHLOG#1: http://paste.ubuntu.com/13447246/
CRASHLOG#2: http://paste.ubuntu.com/13447262/

Temperatures were below 60° Celsius while in kodi and while running memtest86+

Memetest86+:


Thank you very much and good day/night.

[fritsch]

It looks like the crashes happen on shutdown - right?

sudo apt-get install gdb

that will give us more information next time that happens

[teki4u]

Posted memtest86+ screenshot. No errors. Will install gdb and report later. Thanks again

[fritsch]

If you could reproduce the hang with a Debug Log that would be nice - a minimal one, please ... something gets stuck.

[teki4u]

OK, here's a new crash log with gdm installed,this time after exiting kodi (back to command line):
http://paste.ubuntu.com/13466145/

An update about the freeze/hang bug: I copied 2 TV show episodes to internal ssd (path: /home/kodi) to see if with videos stored locally the same problem occurs. One video was hw decoded and the other one software decoded. So far after playing back in the background the 2 copied videos and browsing really hard at it NO freeze, hang or crash happened.
While doing so the box at some point did get up to 75° Celsius and CPU raised to <= 88% and for 1 second I even saw CPU raised to 104%, yet no lag while browsing.

Now it's time to test again with videos in my library linked to my NFS shared HDD but I feel I hurt the drive every time I do this because the box hang becoming unresponsive while using it and I don't know if that can corrupt my HDD.

I setup my /etc/exports file with:
(rw,async,insecure,no_subtree_check), Kodi has direct access to the NFS share so is not using the mount point I have setup in Ubuntu server.

What do think @fritsch?

Edit: Forgot to mention that after my last post I left home and when I came back to test/debug the box was unresponsive, so while on but not in use the box froze/hung again, had to force reboot...
DEBUG LOG: http://paste.ubuntu.com/13478986/

Then when I was under file manager menu setting up sources to copy videos from my HDD to my local ssd, the box froze again, this time rebooted itself... DEBUG LOG: http://paste.ubuntu.com/13463942/

NOTE that is not possible to get short debug logs while trying to reproduce the problem because its random while browsing or after being idle for long hours. The fastest way to reproduce is while playing video in the background and browsing the heck out of it lol.