(2015-08-11, 22:35)Heiko123 Wrote:Quote:2. Fix for power button shutdown
What did you mean.
Is it a predefined gpio pinout ?
# uname -a
Linux rpi512 4.1.4 #1 Tue Aug 11 22:28:29 BST 2015 armv6l GNU/Linux
# vcgencmd version
Aug 10 2015 20:05:05
Copyright (c) 2012 Broadcom
version 010f0680c51cd693b4533061fb19f439451d46e9 (clean) (release)
# lsb_release
OpenELEC (Milhouse) - Version: devel-20150811222741-#0811-gcac5a18 [Build #0811]
# vcdbg log msg 2>&1 | grep DTOK
001572.693: Kernel trailer DTOK property says yes
# Kernel device tree status: Enabled
(2015-08-11, 18:39)doveman2 Wrote: I did notice a fair bit of stuttering and dropped/skipped frames however. When I first checked, I think it was around 479 skipped but I figured that might have been as a result of toggling full-screen, so I restarted the channel and I had a lot less after that but still noticed some gaps in audio and stutters in the video. I'm using MMAL acceleration only and had deinterlace set to Auto. I tried with deinterlace off and that seemed to reduce them but not entirely and even when starting the channel again with deinterlace disabled, there were quite a few gaps in audio for the first few minutes, although it settled down after that. On the third try, I think there were a total of 73 skipped frames (1 dropped) by the time the programme finished and whilst 49 of those occurred with deinterlace on and after I disabled it, that only increased slightly to 52 over the next few minutes, later on there were a couple of obvious stutters/gaps and on checking it had jumped to 63 and the next time, 72.
(2015-08-11, 19:13)popcornmix Wrote:(2015-08-11, 16:26)illiac4 Wrote: and the output after Kodi crash and manual(systemctl stop kodi):
http://sprunge.us/BPPd
Okay, there are some clues in there. The video_decode and image_fx pools are still present, which suggests one of those components hung.
The "qpu_malloc" shows that advanced deinterlace was in progress when it hung.
Can you switch from advanced deinterlace to bob and then grab the same log if it hangs. Then disable deinterlace completely and grab the same log if it hangs.
(2015-08-12, 05:25)illiac4 Wrote: At freeze it has had 40mb left and could not even ssh into pi as it has fully freezed.
(2015-08-12, 06:17)illiac4 Wrote: In my video stream there are no subtitles involved.
(2015-08-12, 06:17)illiac4 Wrote: BTW are for AAS leak already any clues how to fixed it?
(2015-08-12, 13:06)MarkT Wrote: #0811 broke VDR client specific settings (going into OSD will segfault Kodi), switched to OpenELEC-RPi2.arm-6.0-devel-20150808142827-#0808-g75e1b35.tar.
(2015-08-12, 20:28)Leopold Wrote: With #0810 and #0811 my RPi2 becomes completely unresponsive with a black screen when starting an HD live tv channel. I have to pull the plug to reboot it.
There seems to be no problem with the SD channels.
(2015-08-12, 20:42)popcornmix Wrote:(2015-08-12, 20:28)Leopold Wrote: With #0810 and #0811 my RPi2 becomes completely unresponsive with a black screen when starting an HD live tv channel. I have to pull the plug to reboot it.
There seems to be no problem with the SD channels.
What are your overclock settings? Does it work if you remove them?
(2015-08-12, 22:40)Leopold Wrote: After tinkering with removing various overclock settings and eventually restoring the original config, I have been unable to reproduce the issue again. So currently I am able to view HD live tv channels with #0811 when overclocked. I think the screen turns black for longer than it used to before the video starts playing, but that could be my imagination.
# uname -a
Linux rpi512 4.1.4 #1 Thu Aug 13 01:08:47 BST 2015 armv6l GNU/Linux
# vcgencmd version
Aug 13 2015 00:10:56
Copyright (c) 2012 Broadcom
version 2fe75164bde8530ab8e9c384cc0fa4723757ddfa (clean) (release)
# lsb_release
OpenELEC (Milhouse) - Version: devel-20150813010757-#0812-gcac5a18 [Build #0812]
# vcdbg log msg 2>&1 | grep DTOK
001558.313: Kernel trailer DTOK property says yes
# Kernel device tree status: Enabledpopcornmix Wrote:This will give a gpu turbo boost to 300MHz when HD advanced deinterlace, HD MVC, or HD high framerate (> 45 fps) content is played.
This will occur automatically without any config.txt settings needed.
...
The logic is complicated.
Basically for deinterlace v3d will be bumped to 300MHz, but due to PLL dependency all related clocks will be bumped (core, h264, isp by default, just h264 and isp if using avoid_pwm_pll). For the video decode h264 will be bumped (and dependent clocks will be bumped too).
Now if you have your own gpu overclock settings things get more complicated. Each clock will be set to the max of user (e.g. h264_freq) and auto (call it h264_boost = 300). So if you have a big overclock on all gpu clocks, then the auto boost will have no effect (apart from enabling turbo at suitable times).
If you have a partial gpu overclock (e.g. core_freq=500 and h264_freq=250), then it gets more complicated. The core_freq will get 500MHz, which gives a PLL of 2GHz, which means 300MHz is not possible, so h264 will be left at 250MHz. If core_freq was 400MHz, which gives a PLL of 2.4GHz, then 300MHz is possible, so h264 will be boosted to 300MHz.
So, I think you will never be worse off than before, but some user overclocks may have the effect of disabling the auto boost frequency.
