[Forage]

Thanks, the post by popcornmix on that thread was probably what I was thinking of. When I turn off the TV it also sends a shutdown signal to the Pi so that's not going to work for me. I am unable to configure this behaviour as I have nothing showing in peripherals.

What do you mean by "nothing showing in peripherals"? No libcec entry at all or not a setting to prevent the RPi from shutting down?
With just "hdmi_ignore_cec_init=1" as the only CEC related setting in "config.txt" I do have a libcec entry in the peripherals section, so should you.
Do you happen to have any other CEC related settings in "config.txt"? That might prevent the entry from being added.

[Solo0815]

# 1205 hang:
It doesn't hang with systemctl stop kodi from the CLI, but when it is called by a script from advanced launcher.
Advancedlauncher calls retroarch.sh, retroarch.sh calls retroarch.start with

Code:

systemctl stop kodi
retroarch commandline (shortened)
systemctl start kodi

here is the debug-log: http://xbmclogs.com/show.php?id=363796
test was run with clean .kodi and copied back advancedlauncher and retroarch directories

Will do further tests on which version it occurs the first time, so you can track down the issue.

Edit:
The first build showing the hang is #1202

[Milhouse]

Solo0815 - can you PM me a zip of your addons folder (with advancedlauncher/retroarch) and instructions detailing how to run the addon/reproduce the hang?

Tonights build will include an updated splash video player which may avoid hangs.

[Milhouse]

@Solo0815:

Just looking at the "systemctl stop kodi" shutdown process on my system (latest build):

Code:

17:05:22 410.215088 T:3040694272    INFO: Received SIGTERM...
17:05:22 410.215363 T:3040694272   DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc
17:05:22 410.215668 T:3040694272   DEBUG: GOT ANNOUNCEMENT, type: 8, from xbmc, message OnQuit
17:05:22 410.216095 T:3040694272  NOTICE: Storing total System Uptime
17:05:22 410.216736 T:3040694272  NOTICE: Saving settings
17:05:22 410.225281 T:3040678976    INFO: Received SIGTERM...
17:05:22 410.225586 T:3040678976   DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc
17:05:22 410.225891 T:3040678976   DEBUG: GOT ANNOUNCEMENT, type: 8, from xbmc, message OnQuit
17:05:22 410.226379 T:3040678976  NOTICE: Storing total System Uptime
17:05:22 410.227173 T:3040678976  NOTICE: Saving settings

and the same from your system:

Code:

13:38:09 1768.387329 T:3041046528    INFO: Received SIGTERM...
13:38:09 1768.387573 T:3041046528   DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc
13:38:09 1768.422729 T:3041031232    INFO: Received SIGTERM...
13:38:09 1768.423218 T:3041031232   DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc

Two things that stand out:

1) Why are two separate threads both saving settings on shutdown?
2) Your system doesn't seem to handle the OnQuit announcement(s), so chances are the threads are simply hanging at that point

There is also a regression somewhere which results in settings being "lost" and reverting to defaults (guisettings.xml being trashed?) - I wonder if that is related somehow. Can't spend any more time on this today but if you can send me the archive maybe I can reproduce and investigate further tomorrow.

[Milhouse]

@Solo0815: I also notice you're using a 256MB Pi (with 128MB gpu_mem). Have you tried running "configrpi256.sh" as this will enable 128MB of swap, and reduce your gpu_mem to 112 which is the recommended level on a 256MB Pi. Maybe the altered memory characteristics will avoid the hang, as the crashlog facility does alter some limits which may be adversely affecting your Pi.

[Solo0815]

I'm using a 512MB RPi Model B without "+". How do you think that I'm running a 256MB model?

These are the IMHO relevant parts of my config.txt

Code:

# default GPU memory split (do not change if you do not know what you are doing)
  gpu_mem=256

# SDRAM size based GPU memory split, uncomment and setup to override 'gpu_mem'
# gpu_mem_256=128
# gpu_mem_512=128
...
arm_freq=900
core_freq=333
sdram_freq=450
over_voltage=2

# set to 'force_turbo=1' to disable dynamic overclocking (you can lose your warranty!)
  force_turbo=0

I will pack the addon-folders and send you the link via PM.
Please be patient.

[Milhouse]

I'm using a 512MB RPi Model B without "+". How do you think that I'm running a 256MB model?

This, from the log you posted in post #2222:

Code:

13:36:48 1687.554688 T:3041046528  NOTICE: ARM mem: 128MB GPU mem: 128MB MPG2:1 WVC1:1

That suggests you only have a 256MB Pi. Or 256MB of your 512MB has gone AWOL.

Have you got "total_mem=256" set in /flash/config.txt?

[Mydriaze]

popcornmix, Milhouse, thank you very much for your answers. I appreciate.

[Solo0815]

The 256MB setting was "gpu_mem=256"
uncommenting "gpu_mem_512=128" helped to get 512MB displayed.
I thought gpu_mem is the size for the "graphic-buffer" and I get a 256/256 split

KODI-Folder:
here is the .kodi folder: https://dl.dropboxusercontent.com/u/3675...5-kodi.zip
1. replace your .kodi-folder with this one
2. select: Programs > AdvancedLauncher > Default > SNES > Super Bomberman 3
3. you'll get a black screen. The game starts, if you change OE with any build lower than #1202
I hope this helps
Thx for looking into it

[Leopold]

Thanks, the post by popcornmix on that thread was probably what I was thinking of. When I turn off the TV it also sends a shutdown signal to the Pi so that's not going to work for me. I am unable to configure this behaviour as I have nothing showing in peripherals.

What do you mean by "nothing showing in peripherals"? No libcec entry at all or not a setting to prevent the RPi from shutting down?
With just "hdmi_ignore_cec_init=1" as the only CEC related setting in "config.txt" I do have a libcec entry in the peripherals section, so should you.
Do you happen to have any other CEC related settings in "config.txt"? That might prevent the entry from being added.

I tried again and the cec adapter was shown, so that must have been a temporary glitch. I disabled the option that shuts down kodi when the TV is turned off, and now power toggling the TV does fix the media buttons. I'm not sure yet if this is a better solution than hdmi_ignore_cec_init=1 but it's good to know there is another way of working around it. It would be great if a proper fix could be found. When I get a chance I'll try cec_osd_name=kodi.

[Milhouse]

New OpenELEC Helix build: #1206
(Supercedes previous build)

Code:

# uname -a
Linux rpi512 3.17.4 #1 PREEMPT Sat Dec 6 21:01:46 GMT 2014 armv6l GNU/Linux

# vcgencmd version
Dec  3 2014 17:26:22
Copyright (c) 2012 Broadcom
version 23776f83288e23b6d1fc197390f79cf4cc05f558 (clean) (release)

# lsb_release
OpenELEC (Milhouse) - Version: devel-20141206210038-r19739-g497a43b [Build #1206]

Based on tip of OpenELEC master (497a43ba, changelog) and tip of XBMC master (8d4cdb55, 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-3.17.y
  
• Excludes the OpenELEC xbmc-001-newclock4 patch in favour of sourcing these and possibly more recent patches directly from newclock4 branch
  
• Default setting for "Show RSS Feed" changed to disabled (new installs only) [patch details]
  
• Disabled "Total Duration" in Confluence (see build #0221 for details)
  
• Adapted service.openelec.settings to take advantage of PR:5217 [patch details]
  
• Includes latest libnfs master (9c1d3848)
  
• Includes latest libcec master (9f000e43)
  
• Includes latest xbmc-pvr-addons master (5eea1476)
  
• Includes latest xbmc-addon-xvdr master (328fa653)
  
• Includes additional ffmpeg codecs/muxers enabled for testing/benchmarking purposes (see patch)
  
• Includes animated splash support (patch)
  
• Includes commits from libcec-2.2.0 (popcornmix)
  
• Included pastebin: Add device tree kernel trailer
  
• Included pastebin: Enable kernel device-tree support
  
• Included pastebin: Add *.dtb files to firmware
  
• Included PR:3657: [rfc] kodi crashlogs
  
• Includes PR:5573: webserver: improved caching control (see discussion)
  
• Includes PR:5747: [database] - add setting for hiding watched movies/episodes in recently added lists
  
• Includes PR:5752: [jsonrpc] Allow retrieving empty TV shows via VideoLibrary.GetTVShows.
  
• Includes PR:5893: fix getting charset from http header, incorrect usage of constructor for...
  
• Includes PR:5894: [addons] display a more helpful message on python script error
  

Build Highlights:

1. Updated hello_video.bin (used to "play" the splash animation) - please report if it improves the situation (or not):
   

   Been trying to get to the bottom of the splash video hang. I can reproduce it when calling it earlier in systemd boot (e.g. from mounting swap).
   I've found rejigging the order of shutting down openmax fixes it for me.
   
   As it's timing dependant I can't be certain this fixes it, but it hopefully does. I've also changed the layer the video is rendered to to be above kodi which could be useful.

2. Added: PR:5893 and PR:5894
   

Build Details:

1. OpenELEC:
   • update CONTRIBUTING.md (PR:3671, 1 commit, 1 file changed)
     
2. XBMC:
   • [skin] update re-touched skin (8d4cdb55)
     
3. Additional commits/pull requests not yet merged upstream:
   • Added: PR:5893: fix getting charset from http header, incorrect usage of constructor for...
     
   • Added: PR:5894: [addons] display a more helpful message on python script error
     

[Milhouse]

The 256MB setting was "gpu_mem=256"
uncommenting "gpu_mem_512=128" helped to get 512MB displayed.
I thought gpu_mem is the size for the "graphic-buffer" and I get a 256/256 split

Do you still get the hang now that you have a 256/256 split (is this confirmed in your debug log - maybe upload another log?)

KODI-Folder:

Thanks, will take a look at reproducing this tomorrow.

[slack3r]

New OpenELEC Helix build: #1206
(Supercedes previous build)

1. Updated hello_video.bin (used to "play" the splash animation) - please report if it improves the situation (or not):
   

   Been trying to get to the bottom of the splash video hang. I can reproduce it when calling it earlier in systemd boot (e.g. from mounting swap).
   I've found rejigging the order of shutting down openmax fixes it for me.
   As it's timing dependant I can't be certain this fixes it, but it hopefully does. I've also changed the layer the video is rendered to to be above kodi which could be useful.

Video hang is gone. Tested with both animated images. With "6 second white image", animation is incomplete because kodi.service starts too early. But it does not hang anymore. Instead, the black image is perfect.

Thank you.

[Milhouse]

With "6 second white image", animation is incomplete because kodi.service starts too early.

kodi.bin should be waiting for the splash video to play out completely - I've tested with a 10 second video and there is a pause until the video finishes.

When playing a "long" video, do you see kodi waiting at the point where it has output "Checking resolution 16"?

The following is output when starting kodi.service with a 10 second video:

Code:

10:13:24 47047.964844 T:3040784384  NOTICE: Found ([email protected]) at 22, setting to RES_DESKTOP at 16
10:13:24 47047.964844 T:3040784384  NOTICE: Checking resolution 16
10:13:33 47057.417969 T:3040784384  NOTICE: GL_VENDOR = Broadcom

and again with a 6 second video:

Code:

10:17:25 47289.507812 T:3040849920  NOTICE: Found ([email protected]) at 22, setting to RES_DESKTOP at 16
10:17:25 47289.507812 T:3040849920  NOTICE: Checking resolution 16
10:17:31 47295.218750 T:3040849920  NOTICE: GL_VENDOR = Broadcom

and finally with /storage/.config/splash.disable (ie. no splash video):

Code:

10:19:06 47390.230469 T:3041050624  NOTICE: Found ([email protected]) at 22, setting to RES_DESKTOP at 16
10:19:06 47390.230469 T:3041050624  NOTICE: Checking resolution 16
10:19:06 47390.285156 T:3041050624  NOTICE: GL_VENDOR = Broadcom

[slack3r]

kodi.bin should be waiting for the splash video to play out completely - I've tested with a 10 second video and there is a pause until the video finishes.

When playing a "long" video, do you see kodi waiting at the point where it has output "Checking resolution 16"?

Uhm... I do not understand where I can see that kodi.bin is waiting. This the log with a 6 second video:

Code:

01:00:16  16.613705 T:3040620544  NOTICE: Found ([email protected]) at 22, set
ting to RES_DESKTOP at 16
01:00:16  16.614992 T:3040620544  NOTICE: Checking resolution 16
12:17:17  17.955549 T:3040620544  NOTICE: GL_VENDOR = Broadcom
12:17:17  17.955887 T:3040620544  NOTICE: GL_RENDERER = VideoCore IV HW
12:17:17  17.956093 T:3040620544  NOTICE: GL_VERSION = OpenGL ES 2.0

And with splash disabled:

Code:

01:00:16  16.278088 T:3041394688  NOTICE: Found ([email protected]) at 22, set
ting to RES_DESKTOP at 16
01:00:16  16.279510 T:3041394688  NOTICE: Checking resolution 16
01:00:16  16.421019 T:3041394688  NOTICE: GL_VENDOR = Broadcom
01:00:16  16.421247 T:3041394688  NOTICE: GL_RENDERER = VideoCore IV HW
01:00:16  16.421381 T:3041394688  NOTICE: GL_VERSION = OpenGL ES 2.0

GUI is limited to 720p

P.s.
Is my network starting too late?