[vdr] Re: vdr-1.3.13: driver buffer overflows

["C.Y.M" <syphir@syphir.sytes.net>]

Reinhard Nissl wrote:
> Hi,
>
> while debugging a different issue I've discovered the following log 
> entries:
>
> Oct 21 20:44:29 video vdr[25664]: switching to channel 987
> Oct 21 20:44:29 video vdr[25947]: transfer thread ended (pid=25947, 
> tid=393226)
> Oct 21 20:44:29 video vdr[25949]: TS buffer on device 1 thread ended 
> (pid=25949, tid=425996)
> Oct 21 20:44:29 video vdr[25948]: buffer stats: 2444 (0%) used
> Oct 21 20:44:29 video vdr[25948]: receiver on device 1 thread ended 
> (pid=25948, tid=409611)
> Oct 21 20:44:29 video vdr[25664]: cTS2PES got 0 TS errors, 1 TS 
> continuity errors
> Oct 21 20:44:29 video vdr[25664]: buffer stats: 2820 (0%) used
> Oct 21 20:44:29 video vdr[25978]: transfer thread started (pid=25978, 
> tid=442378)
> Oct 21 20:44:29 video vdr[25979]: receiver on device 1 thread started 
> (pid=25979, tid=458763)
> Oct 21 20:44:29 video vdr[25980]: TS buffer on device 1 thread started 
> (pid=25980, tid=475148)
> Oct 21 20:44:34 video vdr[25978]: ERROR: no useful data seen within 
> 10600568 byte of video stream
> Oct 21 20:51:59 video vdr[25980]: buffer usage: 70% (tid=458763)
> Oct 21 20:51:59 video vdr[25980]: buffer usage: 80% (tid=458763)
> Oct 21 20:51:59 video vdr[25980]: buffer usage: 90% (tid=458763)
> Oct 21 20:51:59 video vdr[25980]: buffer usage: 100% (tid=458763)
> Oct 21 20:52:02 video vdr[25980]: ERROR: driver buffer overflow on device 1
> Oct 21 20:52:03 video vdr[25979]: ERROR: skipped 11 bytes to sync on TS 
> packet on device 1
> Oct 21 20:52:04 video vdr[25980]: ERROR: driver buffer overflow on device 1
> Oct 21 20:52:06 video vdr[25979]: ERROR: skipped 11 bytes to sync on TS 
> packet on device 1
> Oct 21 20:52:07 video vdr[25980]: ERROR: driver buffer overflow on device 1
> Oct 21 20:52:08 video vdr[25979]: ERROR: skipped 11 bytes to sync on TS 
> packet on device 1
> Oct 21 20:52:09 video vdr[25980]: ERROR: driver buffer overflow on device 1
> Oct 21 20:52:11 video vdr[25979]: ERROR: skipped 11 bytes to sync on TS 
> packet on device 1
> Oct 21 20:52:12 video vdr[25980]: ERROR: driver buffer overflow on device 1
> Oct 21 20:52:12 video vdr[25664]: switching to channel 986
> Oct 21 20:52:12 video vdr[25978]: transfer thread ended (pid=25978, 
> tid=442378)
> Oct 21 20:52:12 video vdr[25980]: TS buffer on device 1 thread ended 
> (pid=25980, tid=475148)
> Oct 21 20:52:12 video vdr[25979]: buffer stats: 2097151 (100%) used
> Oct 21 20:52:12 video vdr[25979]: receiver on device 1 thread ended 
> (pid=25979, tid=458763)
> Oct 21 20:52:12 video vdr[25664]: cTS2PES got 0 TS errors, 3 TS 
> continuity errors
> Oct 21 20:52:12 video vdr[25664]: cTS2PES got 0 TS errors, 4 TS 
> continuity errors
> Oct 21 20:52:12 video vdr[25664]: buffer stats: 588440 (14%) used
> Oct 21 20:52:12 video vdr[26097]: transfer thread started (pid=26097, 
> tid=491530)
> Oct 21 20:52:12 video vdr[26098]: receiver on device 1 thread started 
> (pid=26098, tid=507915)
> Oct 21 20:52:12 video vdr[26099]: TS buffer on device 1 thread started 
> (pid=26099, tid=524300)
>
>
>
> Some additional information:
> - Channel 987 is Euro1080 (HD1) and I would expect them to broadcast an 
> encrypted stream at the moment.
> - CPU load is high (~ 64 %) since 20:44:29 and caused by process 
> vdr[25979].
> - CPU load reaches maximum (~ 99 %) at 20:51:59 which is caused by 
> processes vdr[25979] and vdr[25980].
>
> Does anybody have an idea what's going wrong here?
>
> Bye.
Reinhard, Im just curious if you are using the dvbdevice patch in your 
vdr source tree as well.  The one that is supposed to help with the 
"FE_HAS_LOCK" issue posted recently by Dominique Simon.

--Snip--