Live tv sometime crashes
#1
I'm using HDHomerun, with TVHeadend 3.9 running on my Synology NAS and Openelec 4.0.7 running on a RaspberryPi and an 4th gen Intel NUC. Now i never have any problems with the Rasp. But with the Intel Nuc i sometimes experience a crash. I recorded an error in de logs which is pasted below.

This happens during a channel change. Or activation of a channel. I cant get anything from the logs other than maybe the display driver?! Does anyone have an idea?

When it happens it results in rebooitng XBMC, not the entire device, just xbmc.

17:34:37 T:139871498786560 ERROR: Get - failed to get stream
17:34:37 T:139871498786560 DEBUG: CDVDPlayer::SetCaching - caching state 2
17:34:37 T:139871498786560 WARNING: CDVDMessageQueue(audio):Tongueut MSGQ_NOT_INITIALIZED
17:34:37 T:139871498786560 WARNING: CDVDMessageQueue(video):Tongueut MSGQ_NOT_INITIALIZED
17:34:37 T:139871498786560 DEBUG: OnPlayBackStarted : play state was 1, starting 1
17:34:37 T:139873348486976 DEBUG: PlayFile : OpenFile succeed, play state 2
17:34:37 T:139873348486976 DEBUG: OnPlayBackStarted : play state was 2, starting 0
17:34:37 T:139873348486976 DEBUG: LIRC: Update - NEW at 408899:160 0 KEY_OK_UP devinput (KEY_OK_UP)
17:34:37 T:139873348486976 DEBUG: CGUIInfoManager::SetCurrentMovie(pvr://channels/tv/Alle TV kanalen/13.pvr)
17:34:37 T:139873348486976 DEBUG: CAnnouncementManager - Announcement: OnPlay from xbmc
17:34:37 T:139873348486976 DEBUG: GOT ANNOUNCEMENT, type: 1, from xbmc, message OnPlay
17:34:38 T:139872505419520 NOTICE: PrimeWire: Service: Playback started
17:34:38 T:139872480335616 DEBUG: AddOnLog: Tvheadend HTSP Client: ParseSubscriptionStart - id: 3, type: H264, codec: 28
17:34:38 T:139872480335616 DEBUG: AddOnLog: Tvheadend HTSP Client: ParseSubscriptionStart - id: 4, type: AC3, codec: 86019
17:34:38 T:139872480335616 DEBUG: AddOnLog: Tvheadend HTSP Client: ParseSubscriptionStart - id: 5, type: MPEG2AUDIO, codec: 86016
17:34:38 T:139872480335616 DEBUG: AddOnLog: Tvheadend HTSP Client: ParseSubscriptionStart - id: 1, type: CA, ignored
17:34:38 T:139872480335616 DEBUG: AddOnLog: Tvheadend HTSP Client: ParseSubscriptionStart - id: 2, type: CA, ignored
17:34:38 T:139872480335616 INFO: AddOnLog: Tvheadend HTSP Client: ParseSubscriptionStart - subscription started on adapter HDHomeRun DVB-C 122139E8-1 : DVB-C #0, mux 770000, network Ziggo, provider Ziggo, service Discovery Channel HD
17:34:38 T:139871498786560 DEBUG: CDVDDemuxPVRClient::RequestStreams(): added/updated stream 0:3 with codec_id 28
17:34:38 T:139871498786560 DEBUG: CDVDDemuxPVRClient::RequestStreams(): added/updated stream 1:4 with codec_id 86019
17:34:38 T:139871498786560 DEBUG: CDVDDemuxPVRClient::RequestStreams(): added/updated stream 2:5 with codec_id 86016
17:34:38 T:139871498786560 NOTICE: Opening video stream: 0 source: 256
17:34:38 T:139871498786560 NOTICE: Creating video codec with codec id: 28
17:34:38 T:139871498786560 DEBUG: CDVDFactoryCodec: compiled in hardware support: CrystalHD:yes AMCodec:no MediaCodec:no OpenMax:no libstagefright:no VDPAU:yes VAAPI:yes
17:34:38 T:139871498786560 DEBUG: FactoryCodec - Video: - Opening
17:34:38 T:139871498786560 NOTICE: CDVDVideoCodecFFmpeg::Open() Using codec: H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
17:34:38 T:139871498786560 DEBUG: FactoryCodec - Video: ff-h264 - Opened
17:34:38 T:139871498786560 NOTICE: Creating video thread
17:34:38 T:139870685034240 NOTICE: Thread DVDPlayerVideo start, auto delete: false
17:34:38 T:139870685034240 NOTICE: running thread: video_thread
17:34:38 T:139871498786560 NOTICE: Opening audio stream: 1 source: 256
17:34:38 T:139871498786560 NOTICE: Finding audio codec for: 86019
17:34:38 T:139870685034240 DEBUG: CDVDPlayerVideo - CDVDMsg::GENERAL_SYNCHRONIZE
17:34:38 T:139871498786560 DEBUG: FactoryCodec - Audio: passthrough - Opening
17:34:38 T:139871498786560 DEBUG: FactoryCodec - Audio: passthrough - Failed
17:34:38 T:139871498786560 DEBUG: FactoryCodec - Audio: FFmpeg - Opening
17:34:38 T:139871498786560 DEBUG: FactoryCodec - Audio: FFmpeg - Opened
17:34:38 T:139871498786560 NOTICE: Creating audio thread
17:34:38 T:139870676641536 NOTICE: Thread DVDPlayerAudio start, auto delete: false
17:34:38 T:139870676641536 NOTICE: running thread: CDVDPlayerAudio:Tonguerocess()
17:34:39 T:139871498786560 DEBUG: ParsePacket - {0} profile changed from -99 to 100
17:34:39 T:139871498786560 DEBUG: ParsePacket - {0} level changed from -99 to 40
17:34:39 T:139871498786560 NOTICE: Opening video stream: 0 source: 256
17:34:39 T:139871498786560 NOTICE: Creating video codec with codec id: 28
17:34:39 T:139871498786560 DEBUG: CDVDFactoryCodec: compiled in hardware support: CrystalHD:yes AMCodec:no MediaCodec:no OpenMax:no libstagefright:no VDPAU:yes VAAPI:yes
17:34:39 T:139871498786560 DEBUG: FactoryCodec - Video: - Opening
17:34:39 T:139871498786560 NOTICE: CDVDVideoCodecFFmpeg::Open() Using codec: H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
17:34:39 T:139871498786560 DEBUG: FactoryCodec - Video: ff-h264 - Opened
17:34:39 T:139870685034240 DEBUG: CDVDPlayerVideo - CDVDMsg::GENERAL_RESYNC(0.000000, 1)
17:34:39 T:139870685034240 DEBUG: CDVDPlayerVideo::CalcDropRequirement - hurry: 0
17:34:39 T:139870685034240 DEBUG: VAAPI - attempting to open codec 28 with profile 100 at level 40 with 3 reference frames
17:34:39 T:139870685034240 DEBUG: VAAPI - initialize version 0.35
17:34:39 T:139870685034240 DEBUG: VAAPI - vendor: Intel i965 driver for Intel® Haswell Mobile - 1.3.2
17:34:39 T:139870685034240 DEBUG: VAAPI - attrib 0 (get/set) min -100 max 100 value 0x0
17:34:39 T:139870685034240 DEBUG: VAAPI - attrib 1 (get/set) min 0 max 100 value 0x32
17:34:39 T:139870685034240 DEBUG: VAAPI - attrib 2 (get/set) min -180 max 180 value 0x0
17:34:39 T:139870685034240 DEBUG: VAAPI - attrib 3 (get/set) min 0 max 100 value 0x32
17:34:39 T:139870685034240 DEBUG: VAAPI - attrib 6 (get/set) min 0 max 3 value 0x0
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 0
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 1
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 13
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 6
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 7
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 8
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 9
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 10
17:34:39 T:139870685034240 DEBUG: VAAPI - profile -1
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 12
17:34:39 T:139870685034240 DEBUG: VAAPI - making sure 9 surfaces are allocated for given 3 references
17:34:39 T:139870685034240 DEBUG: VAAPI - attempting to open codec 28 with profile 100 at level 40 with 3 reference frames
17:34:39 T:139870685034240 DEBUG: VAAPI - attrib 0 (get/set) min -100 max 100 value 0x0
17:34:39 T:139870685034240 DEBUG: VAAPI - attrib 1 (get/set) min 0 max 100 value 0x32
17:34:39 T:139870685034240 DEBUG: VAAPI - attrib 2 (get/set) min -180 max 180 value 0x0
17:34:39 T:139870685034240 DEBUG: VAAPI - attrib 3 (get/set) min 0 max 100 value 0x32
17:34:39 T:139870685034240 DEBUG: VAAPI - attrib 6 (get/set) min 0 max 3 value 0x0
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 0
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 1
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 13
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 6
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 7
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 8
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 9
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 10
17:34:39 T:139870685034240 DEBUG: VAAPI - profile -1
17:34:39 T:139870685034240 DEBUG: VAAPI - profile 12
17:34:39 T:139870685034240 DEBUG: VAAPI - making sure 9 surfaces are allocated for given 3 references
17:34:39 T:139870685034240 DEBUG: VAAPI - destroying surface 0x4000000
17:34:39 T:139870685034240 DEBUG: VAAPI - destroying surface 0x4000001
17:34:39 T:139870685034240 DEBUG: VAAPI - destroying surface 0x4000002
17:34:39 T:139870685034240 DEBUG: VAAPI - destroying surface 0x4000003
17:34:39 T:139870685034240 DEBUG: VAAPI - destroying surface 0x4000004
17:34:39 T:139870685034240 DEBUG: VAAPI - destroying surface 0x4000005
17:34:39 T:139870685034240 DEBUG: VAAPI - destroying surface 0x4000006
17:34:39 T:139870685034240 DEBUG: VAAPI - destroying surface 0x4000007
17:34:39 T:139870685034240 DEBUG: VAAPI - destroying surface 0x4000008
Reply
#2
Post the full crash log to pastebin here, it should be in your home directory.
Reply
#3
The full log is 1.1 GB Confused, but if thats what you need, i'll do it.

Nah, i won't do that Smile there's a lot of rubish in it because a permission issue i had a few days ago.

I've deleted the log file and will post the full log when it happens again.


But you ofcourse mean the log file from XBMC, i'll post it when it happens again.
Reply
#4
Hello
I have the same problem.
Crash log:
http://paste.ubuntu.com/7981952/
Crash thread:
Thread 1 (Thread 0x7f23f1ffb700 (LWP 9901))

Always occurs on HD channels.

Bye
Reply
#5
You two have two totally different problems.

for @sccplg: as you build from source, can you revert:
ac287cc10842f9f04fb23a6aea441db9d6eab5ee

and

bdf9636fb8b8958456002c88f2708e512f9ed253


Does it fix the issue?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#6
Hello.
Thank you fritsch.
I reveted the suggested commits.
Everything seems OK.
Ffmpeg 2.3.1 bug ?

Bye
Reply
#7
Yes - most likely. I will put a link to the initial commit. Thanks for testing.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#8
The real problem here is that it crashes in the intel hw decoding driver, which should never happen whatever ffmpeg pushes down there. If you find time, please report a bug at bugs.freedesktop.org - it might be really useful to add an VAAPI_TRACE to your bugreport.

Please reference the bug in that thread so we can follow it.

Edit: You can do that by doing:
Code:
export LIBVA_TRACE=/your/path/to/the/logfile
xbmc

Thanks much for your help.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#9
Hello.
Just a question:
why keeping unchanged libva and intel driver and only restoring the previous version of ffmpeg the crash does not occur?
I do not want to start a unnecessary discussion.
Thanks
Reply
#10
Their driver is never allowed to crash no matter what you do. It must be "idiot safe" :-)

If you have time, you can also only downgrade libva + libva-driver-intel and test that without the ffmpeg downgraded again. The LIBVA_TRACE will show the issue - be it in ffmpeg or within intel drivers. You can post the libva_trace in that thread before opening the bugreport - perhaps we can see something. And decide to post it to the ffmpeg bugtracker.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#11
Crash log with:

12:59:41 T:140136205322176 NOTICE: Starting Kodi (14.0-ALPHA3 Git:2014-08-11-e561c97-dirty). Platform: Linux x86 64-bit
12:59:41 T:140136205322176 NOTICE: Using Kodi Release x64 build
12:59:41 T:140136205322176 NOTICE: Kodi compiled Aug 11 2014 by GCC 4.8.2 for Linux x86 64-bit version 3.13.11 (199947)
12:59:41 T:140136205322176 NOTICE: Running on Ubuntu 14.04.1 LTS, kernel: Linux x86 64-bit version 3.15.9-031509-generic
12:59:41 T:140136205322176 NOTICE: FFmpeg statically linked, version: 14.0a2-Helix-293-ge561c97-xbmc-2.3.1-Helix-alpha2
12:59:41 T:140136205322176 NOTICE: Host CPU: Intel® Core™ i3-2105 CPU @ 3.10GHz, 4 cores available

vainfo:

libva info: LIBVA_TRACE is on, save log into /home/pierluigi/log.41574.014e55b0
libva info: VA-API version 0.35.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_35
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.35 (libva 1.3.2.pre1)
vainfo: Driver version: Intel i965 driver for Intel® Sandybridge Desktop - 1.3.3.pre1
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc

Smile KODY crash log:
http://paste.ubuntu.com/8016170/

LIBVA_TRACE:
http://paste.ubuntu.com/8016180/
---
Downgrading libva and intel-drv to staging version

vainfo:

libva info: LIBVA_TRACE is on, save log into /home/pierluigi/log.44667.024795c0
libva info: VA-API version 0.34.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_34
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.34 (libva 1.2.0.pre1)
vainfo: Driver version: Intel i965 driver for Intel® Sandybridge Desktop - 1.0.21.pre1
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc

Smile KODY crash log:
http://paste.ubuntu.com/8016613/

LIBVA_TRACE:
http://paste.ubuntu.com/8016615/

The behavior looks the same. HuhHuhHuh
Reply
#12
"staging" is highly not suggested. Please stay on libva master.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#13
I think filing that one with latest master libva on bugs.freedesktop.org is the way to go. As the intel folks are also maintaining the hwaccel in ffmpeg it will get handled correctlyo ver there. You can mention that downgrading of ffmpeg to 2.2.x fixes the issue. That's the intel part, cause the driver is never allowed to segfault.

You can additionally file a bug with the ffmpeg people as it's a regression from 2.2.x

Don't forget to post the bugtracker urls here.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#14
VA-API version: 0.35 (libva 1.3.2.pre1)
and
Intel i965 driver for Intel® Sandybridge Desktop - 1.3.3.pre1
They are both compiled from the master.

For segmentation fault in i965_drv_video.so:
https://bugs.freedesktop.org/show_bug.cgi?id=82466

Bye
Reply
#15
I havent experienced this error for a while now. I do have upgraded my Openelec 4.0.7 to 4.1.2 and a few days ago to the latest beta 4.1.3. I believe it's using 2.3.x of ffdmpeg.
Reply

Logout Mark Read Team Forum Stats Members Help
Live tv sometime crashes0