> >>>>> I have experienced this problem several times today while on HD h264 > >>>>> channels. Like previously posted: > >>>>> > >>>>> Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) > >>>>> Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) > >>>>> Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) > >>>>> Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) > >>>>> > >>>>> VDR was unresponsive and had to be restarted to fix. > >>>>> > >>>>> Best regards, > >>>>> Derek > >>>> > >>>> Sorry, forgot to mention this is with VDR-1.7.13... > >>> > >>> > >>> I confirm - with vdr 1.7.13 still have the same issue > >> > >> I assume, you both use vdr-xine. It would be a good idea to > >> create a backtrace in that situation to rule out vdr-xine as > >> source of this issue. > > > > yes, I'm using the vdr-xine 093 > > please advice how should I use backtrace > > When VDR is unresponsive, type something like that: > > gdb /path/to/vdr `pidof vdr` > > At the gdb prompt, issue the following command: > > thread apply all bt > > and provide the output. but with my buffer overflow problem the vdr is working without any deadlock. I can such messages only in syslog. That's why I can't do backtrace Goga _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
