Kodi Community Forum

(2015-05-21, 16:36)Milhouse Wrote: [ -> ]

(2015-05-21, 15:53)Leopold Wrote: [ -> ]I thought the point of the patch was to delay the HDMI mode change until the hello_video.bin process is no longer running? If so then I don't see how that's possible.

Indeed, but you said "Here's one where the hdmi mode changed before the video ended." so somehow the HDMI mode is changing before the video has played out, which might be upsetting the very simple video player used to display the splash video. I'm only guessing though.

Sorry I seem to have confused things with that statement. I should have said completed instead of ended .

I originally thought that the video may still be playing while the screen goes black during the video mode change, prior to the Kodi gui appearing. From the logging and the patched code I can now see that is not the case and that the video must be terminating before the hdmi mode change.

(2015-05-21, 16:22)Milhouse Wrote: [ -> ]@popcornmix: just noticed in the last few logs that have been posted (and also my own) that the default cacheMemBufferSize is being set to 2MB on RPi2 systems with plenty of available ARM mem - shouldn't this be 20MB?

I can confirm: on my Pi2 cache does not exceed 2MB.

(2015-05-21, 17:02)Leopold Wrote: [ -> ]I originally thought that the video may still be playing while the screen goes black during the video mode change, prior to the Kodi gui appearing. From the logging and the patched code I can now see that is not the case and that the video must be terminating before the hdmi mode change.

I'll modify the kodi-splash.sh script in the next build and capture stderr/stdout from the video player to /tmp/splash.log, maybe it's segfaulting.

If it is segfaulting, with the next build a core will be dumped into /storage/.cache/cores - upload the stacktraces as follows:

Hi,

Everytime I select live TV, kodi freezes and then reboots. Which log do I need to upload to show the crash?

Thanks

(2015-05-21, 16:22)Milhouse Wrote: [ -> ]@popcornmix: just noticed in the last few logs that have been posted (and also my own) that the default cacheMemBufferSize is being set to 2MB on RPi2 systems with plenty of available ARM mem - shouldn't this be 20MB?

Code:

14:02:36   8.754464 T:1967771648  NOTICE: ARM mem: 656MB GPU mem: 352MB MPG2:0 WVC1:0
14:02:36   8.754519 T:1967771648  NOTICE: cacheMemBufferSize: 2MB

Looking at the patch, is the m_arm_mem variable in line 70 the same m_arm_mem variable in line 50?

Okay, I see this. I think I know what it is, but I'm doing a clean build so will take a little while to confirm.

(2015-05-21, 18:45)Marshy33 Wrote: [ -> ]Hi,

Everytime I select live TV, kodi freezes and then reboots. Which log do I need to upload to show the crash?

Thanks

The crashlog - upload the latest file with the following ssh command:

(2015-05-21, 18:49)Milhouse Wrote: [ -> ]

(2015-05-21, 18:45)Marshy33 Wrote: [ -> ]Hi,

Everytime I select live TV, kodi freezes and then reboots. Which log do I need to upload to show the crash?

Thanks

The crashlog - upload the latest file with the following ssh command:

Code:

paste $(ls -1 /storage/.kodi/temp/kodi_crashlog* | tail -1)

Thankyou for the quick reply, here is the log...

http://pastebin.com/V65rghmH

I first set up live TV on 512(I believe) and it worked fine, then after updating to a newer version, the crashes started happening.

@Marshy33: Try deleting your EPG database with:
and restart Kodi.

If that doesn't work, you'll need to contact the maintainer of your PVR client.

(2015-05-21, 19:03)Milhouse Wrote: [ -> ]@Marshy33: Try deleting your EPG database with:

Code:

rm /storage/.kodi/userdata/Database/Epg10.db

and restart Kodi.

If that doesn't work, you'll need to contact the maintainer of your PVR client.

Thankyou again. I have tried what you suggested but still no luck.

I will contact the maintainer of the PVR client.

Really appreciate the help you give on this forum.

New OpenELEC Isengard build #0521: RPi / RPi2
(Supercedes previous build)


Based on tip of OpenELEC master (cf51d162, changelog) and tip of XBMC master (da65bf6b, changelog) with the following modifications:

• Includes newclock4 patches
  
• Excludes the OpenELEC fernetmenta patches due to conflicts with newclock4
  
• Excludes the OpenELEC linux-01-RPi_support patch in favour of sourcing these and possibly more recent patches directly from kernel branch rpi-4.0.y
  
• Default setting for "Show RSS Feed" changed to disabled (new installs only) [patch details]
  
• Disabled "Total Duration" in Confluence (see build #0221 for details)
  
• Includes latest dcadec master (1d714d86, ahead +10)
  
• Includes latest kodi-platform master (33b6390b, ahead +1)
  
• Includes latest libcec master (18555911, ahead +5)
  
• Includes latest libnfs master (77e3d80f, ahead +9)
  
• Includes latest platform master (aafa6e9f)
  
• Includes latest addons: pvr.argustv (cffc8b6b, +1), pvr.demo (9c400e19, +1), pvr.dvblink (3f07ea97, +1), pvr.dvbviewer (05e76da7, +1), pvr.filmon (3f173ec1, +1), pvr.hts (86eb1cc2, +1), pvr.iptvsimple (191972cf, +1), pvr.mediaportal.tvserver (bcfb46f9, +1), pvr.mythtv (6fb769da, +1), pvr.nextpvr (74168dc9, +1), pvr.njoy (9aa05103, +1), pvr.pctv (804dc37c, +1), pvr.stalker (0d6a5d8b, +1), pvr.vbox (83f27246, +3), pvr.vdr.vnsi (824a8a4c), pvr.vuplus (cdc1d0e3, +2), pvr.wmc (42fb669d, +1)
  
• Includes commits from shairplay/master, ahead +17 (juhovh)
  
• Exclude kodi-999.20-PR7102.patch: Temporarily revert dcadec settings and use newclock4 version
  
• Exclude kodi-999.21-configure.ac-dont-break-if-dcadec-is-missing-dcadec-.patch: Temporarily revert due to breakage
  
• Include patch: Enable vcsm kernel options for HEVC optimisations
  
• Include patch: Enable the mailbox driver (new kernel options)
  
• Include patch: Add ffmpeg dependency and includes for HEVC optimisations
  
• Include patch: Add experimental splash video
  
• Include patch: Enable pvr addons
  
• Include PR:6732: [pvr] fixed crash when multiple add-on instances get registered
  
• Include PR:6919: added: also hide thumbs for unwatched episodes if option to show plot is off
  
• Include PR:7048: videodb: Don't allow column value length to exceed key size of unique index
  
• Include PR:7093: [AirTunes] - features
  

Build Highlights:

1. Shadertoy improvements
   
2. Temporarily add /tmp/splash.log logging, and core dump capability, to kodi-splash.sh
   

Build Details:

1. dcadec:
   • Refactor core extension sync word checks. (5a93570a)
     
   • Make core extension parsing more robust. (ec3ee289)
     
   • Fix core profile reporting. (92af012b)
     
   • Change core info structure. (1d714d86)
     
2. newclock4:
   • New commits in this build:
     • [visualisation] Improvements to shadertoy (caee07b7)
       
3. kernel 4.0.y:
   • New commits in this build:
     • vchiq: Change logging level for inbound data (03d42eb7)
       
4. Additional commits/pull requests/changes not yet merged upstream:
   • Updated: patch: Add experimental splash video
     

@Leopold/@ivota:

Can you configure your systems as you would normally, so that the splash doesn't fully play out, then upgrade to build #0521.

Once booted into build #0521, and after the splash video has failed to play to completion, can you paste the contents of /tmp/splash.log into this thread.

If it's just
then there is no error and the video player actually completed successfully, which right now would be a little surprising.

However if the contents of /tmp/splash.log is something like:
then you should have a core file in /storage/.cache/cores - please upload the stacktraces with the following command:

build #0521
/tmp/splash.log = RES: 0

psmon.log
http://sprunge.us/XGMB

(2015-05-21, 23:52)ivota Wrote: [ -> ]build #0521
/tmp/splash.log = RES: 0

psmon.log
http://sprunge.us/XGMB

Thanks, doesn't look like it's seg faulting, so I'm at a loss.

http://sprunge.us/FPcY

/tmp/splash.log

No core file

So the process ran for about 3 seconds instead of the full 6 seconds that is expected for normal execution, but still returned an exit status of zero. Strange.
Is this the code for the included hello_video.bin?

In last few builds i see that during watching live tv pi just freezes.
The log was 440 mb big so these are just last lines before it freezes if this is helpful at all.

The last part before freeze:
http://pastebin.com/Z8JNSgXj


This is the first part of sys info:
http://pastebin.com/wDBxy4gb