[vdr] vdr-1.7.11 (+ vdr-xine) segfaults

Reinhard Nissl rnissl at gmx.de
Tue Jan 26 21:30:58 CET 2010


Hi,

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 2.6.31.8-0.1-desktop x86_64 [ openSUSE 11.2 ]

rpm -q gcc gcc44 glibc
gcc-4.4-4.2.x86_64
gcc44-4.4.1_20090817-2.3.4.x86_64
glibc-2.10.1-10.4.x86_64

A sample from my logs:
Jan 26 20:54:01 corei7 vdr: [7376] switching to channel 7
Jan 26 20:54:03 corei7 vdr: [7430] cVideoRepacker: switching to
MPEG1/2 mode
Jan 26 20:54:03 corei7 vdr: [7430] cVideoRepacker: operating in
MPEG1/2 mode

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.

Bye.
-- 
Dipl.-Inform. (FH) Reinhard Nissl
mailto:rnissl at gmx.de



More information about the vdr mailing list