[vdr] how to find out the crash of vdr
Hi I have vdr 170 + cvs xineliboutput + external svn ffmpeg + hg xine-lib-1.2 during of watching some hdtv channels I have crash ffmpeg/xine-lib with this errors [h264 @ 0x8706aa0]B picture before any references, skipping [h264 @ 0x8706aa0]decode_slice_header error [h264 @ 0x8706aa0]no frame! [h264 @ 0x8706aa0]B picture before any references, skipping [h264 @ 0x8706aa0]decode_slice_header error [h264 @ 0x8706aa0]no frame! [h264 @ 0x8706aa0]B picture before any references, skipping [h264 @ 0x8706aa0]decode_slice_header error [h264 @ 0x8706aa0]no frame! [h264 @ 0x8706aa0]B picture before any references, skipping [h264 @ 0x8706aa0]decode_slice_header error [h264 @ 0x8706aa0]no frame! [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]mmco: unref short failure [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe vdr: osdflush: n: 1, 10.1, timeout: 0, result: 0 [h264 @ 0x8706aa0]warning: first frame is no keyframe vdr: osdflush: n: 2, 22.2, timeout: 0, result: 0 [h264 @ 0x8706aa0]warning: first frame is no keyframe vdr: osdflush: n: 2, 22.6, timeout: 0, result: 0 [h264 @ 0x8706aa0]warning: first frame is no keyframe vdr: osdflush: n: 3, 38.5, timeout: 0, result: 0 [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe vdr: osdflush: n: 1, 9.5, timeout: 0, result: 0 [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]Internal error, picture buffer overflow Aborted How can I track this errors for good bug-report to ffmpeg developpers ? It's seems need to use the gdb. Is it right way ? http://xinehq.de/index.php/developer Q: How do I run xine in gdb? A: First make sure you have a debug build. You can either run xine from gdb or attach to an already-running process: Running xine from gdb: $ gdb xine (gdb) handle SIG32 noprint nostop (gdb) run Attaching to a running xine process: $ gdb xine `pidof xine` ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [linux-dvb] DVB-S2 / Multiproto and future modulation support
Steven Toth wrote: Regarding the multiproto situation: A number of developers, maintainers and users are unhappy with the multiproto situation, actually they've been unhappy for a considerable amount of time. The linuxtv developer community (to some degree) is seen as a joke and a bunch in-fighting people. Multiproto is a great demonstration of this. [1] The multiproto project has gone too far, for too long and no longer has any credibility in the eyes of many people. In response, a number developers have agreed that enough is enough and it's time to take a new direction, for these developers the technical, political and personal cost of multiproto is too high. These developers have decided to make an announcement. Mauro Chehab, Michael Krufky, Patrick Boettcher and myself are hereby announcing that we no longer support multiproto and are forming a smaller dedicated project group which is focusing on adding next generation S2/ISDB-T/DVB-H/DVB-T2/DVB-SH support to the kernel through a different and simpler API. Basic patches and demo code for this API is currently available here. http://www.steventoth.net/linux/s2 Does it even work? Yes Is this new API complete? No Is it perfect? No, we've already had feedback on structural and namingspace changes that people would like to see. Does it have bugs? Of course, we have a list of things we already know we want to fix. but ... Is the new approach flexible? Yes, we're moving away from passing fixed modulation structures into the kernel. Can we add to it without breaking the future ABI when unforseen modulations types occur? Yes Does it preserve backwards compatibility? Yes Importantly, is the overall direction correct? Yes Does it impact existing frontend drivers? No. What's the impact to dvb-core? Small. What's the impact to application developers? None, unless an application developer wants to support the new standards - binary compatibility! We want feedback and we want progress, we aim to achieve it. Importantly, this project group seeks your support. If you also feel frustrated by the multiproto situation and agree in principle with this new approach, and the overall direction of the API changes, then we welcome you and ask you to help us. Growing the list of supporting names by 100%, and allowing us to publish your name on the public mailing list, would show the non-maintainer development community that we recognize the problem and we're taking steps to correct the problem. We want to make LinuxTV a perfect platform for S2, ISDB-T and other advanced modulation types, without using the multiproto patches. We're not asking you for technical help, although we'd like that :) , we're just asking for your encouragement to move away from multiproto. If you feel that you want to support our movement then please help us by acking this email. Regards - Steve, Mike, Patrick and Mauro. Acked-by: Patrick Boettcher [EMAIL PROTECTED] Acked-by: Michael Krufky [EMAIL PROTECTED] Acked-by: Steven Toth [EMAIL PROTECTED] Acked-by: Mauro Carvalho Chehab [EMAIL PROTECTED] * [1]. Rather than point out the issues with multiproto here, take a look at the patches and/or read the comments on the mailing lists. Guys, I don't like the way you do this. ;-( Why didn't you propose this API when we reviewed multiproto? Meanwhile there are applications (vdr, others?) which implement the multiproto API. As I am not willing to spend a single minute of my time with API wars, I will ack this API only if the multiproto developer and the users agree with this approach. Oliver -- VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-restarts after upgrade
Hi, Oliver Joa wrote: Hi, i recently upgraded my vdr to version 1.6.0. Now my vdr restarts every some minutes when recording: Aug 4 12:17:21 video1 vdr: [3688] frontend 1 timed out while tuning to channel 1, tp 111836 Aug 4 12:17:43 video1 vdr: [3694] ERROR: video data stream broken Sometimes it is working, and sometimes it restartes every minute. A friend of me had the same problem when recording ARD. He upgraded his kernel to 2.6.26 and now it works for him. I also tried 2.6.25.9 and 2.6.26.1, but it does not work. I don't think that it is a problem of temperature, because it also happens suddenly after cold startup. The system is running now for some years, with regular software-upgrades. I use Debian-Etch. I got the Problem. The LNB was damaged. One of the 4 Connectors on the Quad-LNB did not work correctly anymore. I changed it and now everything works fine. Thanks Olli ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [linux-dvb] DVB-S2 / Multiproto and future modulation support
On Sat, Aug 30, 2008, Oliver Endriss wrote: Steven Toth wrote: http://www.steventoth.net/linux/s2 Guys, I don't like the way you do this. ;-( Why didn't you propose this API when we reviewed multiproto? Meanwhile there are applications (vdr, others?) which implement the multiproto API. The proposal isn't new, there was some discussion on the list in Nov 2007. For reasons unknown to me I cannot find Steve's original mail on the topic in the list archives, but here's my reply: http://linuxtv.org/pipermail/linux-dvb/2007-November/021618.html http://article.gmane.org/gmane.linux.drivers.dvb/37214 Johannes ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
