[vdr] vdr-1.7.11 (+ vdr-xine) segfaults
rnissl at gmx.de
Tue Jan 26 21:30:58 CET 2010
Am 26.01.2010 19:18, schrieb Jouni Karvo:
> I included logs, please let me know what to try next.
Both of your so far posted logs show this scenario:
> Jan 26 19:54:55 vdr vdr: [-1] buffer usage: 70% (tid=-1)
> Jan 26 19:54:55 vdr vdr: [-1] buffer usage: 80% (tid=-1)
> Jan 26 19:54:55 vdr vdr: [-1] buffer usage: 90% (tid=-1)
> Jan 26 19:54:56 vdr vdr: [-1] buffer usage: 100% (tid=-1)
> Jan 26 19:55:24 vdr vdr: [-1] ERROR: video data stream broken
> Jan 26 19:55:24 vdr vdr: [-1] initiating emergency exit
> Jan 26 19:55:29 vdr vdr: [-1] PANIC: watchdog timer expired - exiting!
This doesn't look like a vdr-xine issue.
But before investigating this further, you first need to fix your
system so that VDR can retrieve thread IDs. As the above log
reports -1 as thread ID it is almost impossible to tell, which
thread got stuck -- either the thread which does the recording or
the other which talks to xine.
Please tell a little bit about your system. I wonder how moving
to x86_64 could result in such mess. Some infos about my system:
Linux 126.96.36.199-0.1-desktop x86_64 [ openSUSE 11.2 ]
rpm -q gcc gcc44 glibc
A sample from my logs:
Jan 26 20:54:01 corei7 vdr:  switching to channel 7
Jan 26 20:54:03 corei7 vdr:  cVideoRepacker: switching to
Jan 26 20:54:03 corei7 vdr:  cVideoRepacker: operating in
And a request for further debug information: please provide it in
a way that it doesn't get wrapped around. Wrapping makes it hard
to read. Simply attach it as plain text file if you cannot find
another way to achieve this.
Dipl.-Inform. (FH) Reinhard Nissl
mailto:rnissl at gmx.de
More information about the vdr