[vdr] Still problems with streamdev-0.3.1

["Sebastian Frei" <sebastian@schnapsleichen.de>]

Hi,

even with the new version of the streamdev plugin, my problem persists:

After a watching a while tv on my streamdev-client (today 1h), the server
plugin stops delivering a stream.
I know this because rebooting the client gives me "channel not available". I
have to restart the server.
Trying to get a stream with the VDR streamingcontrol tool doesn't work too.

The server is a dual card system (FF1.6, Nova) and the client has a dxr3.

When the error on the client occured, no one was using the server. This
error is very annoying, especially
when it occurs at 20:16 and I can't interrupt the server.

Looking at the log files shows that at a certain point the Pid streamer
thread just doesn't want to start anymore.

The server log:

Feb 27 18:22:39 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:22:39 SERVER vdr[95]: Streamdev: Setting data connection to
192.168.1.7:32832
Feb 27 18:22:39 SERVER vdr[95]: Streamdev: Detaching streamer for device
selection
Feb 27 18:22:39 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:22:39 SERVER vdr[869]: Streamdev: Pid streamer thread started
(pid=869)
Feb 27 18:22:39 SERVER vdr[870]: receiver thread started on device 2
(pid=870)
Feb 27 18:22:47 SERVER vdr[95]: Streamdev: Detaching streamer for device
selection
Feb 27 18:22:47 SERVER vdr[869]: Streamdev: Pid streamer thread stopped
Feb 27 18:22:47 SERVER vdr[870]: receiver thread ended on device 2 (pid=870)
Feb 27 18:22:47 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:22:47 SERVER vdr[871]: Streamdev: Pid streamer thread started
(pid=871)
Feb 27 18:22:49 SERVER vdr[871]: Streamdev: Pid streamer thread stopped
Feb 27 18:22:49 SERVER vdr[95]: buffer stats: 19740 (0%) used
Feb 27 18:22:49 SERVER vdr[95]: Streamdev: Detaching streamer for device
selection
Feb 27 18:22:49 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:22:49 SERVER vdr[95]: Streamdev: Setting data connection to
192.168.1.7:32833
Feb 27 18:22:49 SERVER vdr[95]: Streamdev: Detaching streamer for device
selection
Feb 27 18:22:49 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:22:51 SERVER vdr[95]: Streamdev: Detaching streamer for device
selection
Feb 27 18:22:51 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:22:52 SERVER vdr[95]: buffer stats: 0 (0%) used
Feb 27 18:22:52 SERVER vdr[95]: Streamdev: Detaching streamer for device
selection
Feb 27 18:22:52 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:22:52 SERVER vdr[95]: Streamdev: Setting data connection to
192.168.1.7:32834
Feb 27 18:22:52 SERVER vdr[95]: Streamdev: Detaching streamer for device
selection
Feb 27 18:22:52 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:23:00 SERVER vdr[95]: buffer stats: 0 (0%) used
Feb 27 18:23:00 SERVER vdr[95]: Streamdev: Detaching streamer for device
selection
Feb 27 18:23:00 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:23:00 SERVER vdr[95]: Streamdev: Setting data connection to
192.168.1.7:32835
Feb 27 18:23:00 SERVER vdr[95]: Streamdev: Detaching streamer for device
selection
Feb 27 18:23:00 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:23:04 SERVER vdr[95]: buffer stats: 0 (0%) used
Feb 27 18:23:12 SERVER vdr[95]: Streamdev: Detaching streamer for device
selection
Feb 27 18:23:12 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:23:12 SERVER vdr[95]: Streamdev: Setting data connection to
192.168.1.7:32836
Feb 27 18:23:12 SERVER vdr[95]: Streamdev: Detaching streamer for device
selection
Feb 27 18:23:12 SERVER vdr[95]: Streamdev: Reattaching transceiver after
device selection
Feb 27 18:23:13 SERVER vdr[95]: buffer stats: 0 (0%) used
Feb 27 18:23:13 SERVER vdr[95]: Streamdev: Closing connection to
192.168.1.7:32786

The client log:

Feb 27 18:22:20 VDR vdr[491]: transfer thread started (pid=491)
Feb 27 18:22:20 VDR vdr[492]: receiver thread started on device 6 (pid=492)
Feb 27 18:22:32 VDR vdr[242]: switching to channel 12
Feb 27 18:22:32 VDR vdr[491]: transfer thread ended (pid=491)
Feb 27 18:22:33 VDR em8300_video.o: Video sync rdptr is stuck at 0x0001a2e9,
wrptr 0x0001a3e3, left
Feb 27 18:22:33 VDR em8300_video.o: Video sync timeout
Feb 27 18:22:33 VDR vdr[492]: receiver thread ended on device 6 (pid=492)
Feb 27 18:22:33 VDR vdr[242]: cTS2PES got 0 TS errors, 2 TS continuity
errors
Feb 27 18:22:33 VDR vdr[242]: cTS2PES got 0 TS errors, 1 TS continuity
errors
Feb 27 18:22:33 VDR vdr[242]: cTS2PES got 0 TS errors, 2 TS continuity
errors
Feb 27 18:22:33 VDR vdr[242]: buffer stats: 28576 (0%) used
Feb 27 18:22:33 VDR vdr[493]: transfer thread started (pid=493)
Feb 27 18:22:33 VDR vdr[494]: receiver thread started on device 6 (pid=494)
Feb 27 18:22:36 VDR vdr[242]: switching to channel 13
Feb 27 18:22:36 VDR vdr[493]: transfer thread ended (pid=493)
Feb 27 18:22:37 VDR em8300_video.o: Video sync rdptr is stuck at 0x00038ae0,
wrptr 0x00038bda, left
Feb 27 18:22:37 VDR em8300_video.o: Video sync timeout
Feb 27 18:22:37 VDR vdr[494]: receiver thread ended on device 6 (pid=494)
Feb 27 18:22:37 VDR vdr[242]: cTS2PES got 0 TS errors, 1 TS continuity
errors
Feb 27 18:22:37 VDR vdr[242]: buffer stats: 23500 (0%) used
Feb 27 18:22:37 VDR vdr[495]: transfer thread started (pid=495)
Feb 27 18:22:37 VDR vdr[496]: receiver thread started on device 6 (pid=496)
Feb 27 18:22:46 VDR vdr[242]: switching to channel 14
Feb 27 18:22:46 VDR vdr[495]: transfer thread ended (pid=495)
Feb 27 18:22:47 VDR em8300_video.o: Video sync rdptr is stuck at 0x0000c1ca,
wrptr 0x0000c2c4, left
Feb 27 18:22:47 VDR em8300_video.o: Video sync timeout
Feb 27 18:22:47 VDR vdr[496]: receiver thread ended on device 6 (pid=496)
Feb 27 18:22:47 VDR vdr[242]: cTS2PES got 1 TS errors, 1 TS continuity
errors
Feb 27 18:22:47 VDR vdr[242]: cTS2PES got 0 TS errors, 1 TS continuity
errors
Feb 27 18:22:47 VDR vdr[242]: cTS2PES got 0 TS errors, 1 TS continuity
errors
Feb 27 18:22:47 VDR vdr[242]: buffer stats: 23876 (0%) used
Feb 27 18:22:48 VDR vdr[497]: transfer thread started (pid=497)
Feb 27 18:22:48 VDR vdr[498]: receiver thread started on device 6 (pid=498)
Feb 27 18:22:50 VDR vdr[242]: switching to channel 15
Feb 27 18:22:50 VDR vdr[497]: transfer thread ended (pid=497)
Feb 27 18:22:51 VDR em8300_video.o: Video sync rdptr is stuck at 0x0000dc01,
wrptr 0x0000dcfb, left
Feb 27 18:22:51 VDR em8300_video.o: Video sync timeout
Feb 27 18:22:51 VDR vdr[498]: receiver thread ended on device 6 (pid=498)
Feb 27 18:22:51 VDR vdr[242]: buffer stats: 0 (0%) used
Feb 27 18:22:51 VDR vdr[499]: transfer thread started (pid=499)
Feb 27 18:22:51 VDR vdr[500]: receiver thread started on device 6 (pid=500)
Feb 27 18:22:58 VDR vdr[242]: switching to channel 1
Feb 27 18:22:58 VDR vdr[499]: transfer thread ended (pid=499)
Feb 27 18:22:58 VDR em8300_video.o: Video sync rdptr is stuck at 0x0000dc01,
wrptr 0x0000dcfb, left
Feb 27 18:22:58 VDR em8300_video.o: Video sync timeout
Feb 27 18:22:59 VDR vdr[500]: receiver thread ended on device 6 (pid=500)
Feb 27 18:22:59 VDR vdr[242]: buffer stats: 0 (0%) used
Feb 27 18:22:59 VDR vdr[501]: transfer thread started (pid=501)
Feb 27 18:22:59 VDR vdr[502]: receiver thread started on device 6 (pid=502)
Feb 27 18:23:02 VDR vdr[242]: Power button pressed
Feb 27 18:23:03 VDR vdr[501]: transfer thread ended (pid=501)
Feb 27 18:23:03 VDR vdr[502]: receiver thread ended on device 6 (pid=502)
Feb 27 18:23:03 VDR em8300_video.o: Video sync rdptr is stuck at 0x0000dc01,
wrptr 0x0000dcfb, left
Feb 27 18:23:03 VDR em8300_video.o: Video sync timeout
Feb 27 18:23:04 VDR vdr[242]: buffer stats: 0 (0%) used



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.