Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vdr] Re: vdr-1.3.17: thread issues with vdr-streamdev



Rainer Zocholl <UseNet-Posting-Nospam-74308-@zocki.toppoint.de> writes:

>>grrr i hate this. again it doesn't work here ! :-(
> Have you done
> make plugins-clean clean
> ?

sure

>>vdr[1100]: ERROR: thread 557064 won't end (waited 3 seconds) -
>>cancelling it...
> Which compiler, library, CPU speed, cards?

it's a debian unstable box, so
gcc is 3.3.5
libc6 is 2.3.2.ds1 (optimized i686 installed as well, not used since
i'm using a 2.4 kernel)
kernel is now running 2.4.29-pre1 + latest dvb-kernel (2_4_branch)
first card is TT FF dvb-s v1.5 ( diseqc: A=S28.E B=S19.2E )
second one is TT budget (without ci) dvb-s ( S28.E )
diskless, headless, the third pci card is the ethernet one
cpu is a p3 1GHz box (same issues with a p3 600EB underclocked to
4.5*66MHz)


>>and streamdev-server doesn't transmit anything.
>>It appears to be better without that patch :(
> Have you applied the thread safe patches?

yep, i've just restarted from a fresh vdr. For the tests, i'm only
going to use streamdev-server and http streaming. (using wget -O
/dev/null -Y off http://vdr:3000/channel_number)

vdr-1.3.17
+ streamdev 0.3.3-pre3-geni +
    vdr-streamdev-0.3.3-pre3-geni-for-1.3.14up-patch-0.3
+ vdr-1.3.17-safe-threading-patches-diff (thx to CYM)
+ poison-non-thread_streamdev
+ vdr-1.3.4-SourceCaps.patch

I experience a lot of "ERROR: thread 196616 won't end (waited 3
seconds) - cancelling it..." messages.
It's weird because depending on the channel i'd the behavior is not
the same.

[ the ff card is adapter0 ]
starting vdr with -D 0: whatever the channel i watch (S28 or S19) it
works perfectly, without any thread ERROR.
<vdr log>
Dec  6 14:07:14 dvb vdr[5354]: Streamdev: Accepted new client (HTTP)
10.0.2.2:35371
Dec  6 14:07:14 dvb vdr[5356]: transfer thread started (pid=5356,
tid=81926)
Dec  6 14:07:14 dvb vdr[5357]: receiver on device 1 thread started
(pid=5357, tid=98311)
Dec  6 14:07:14 dvb vdr[5358]: TS buffer on device 1 thread started
(pid=5358, tid=114696)
Dec  6 14:07:14 dvb vdr[5359]: Streamdev: Live streamer thread started
(pid=5359, tid=131081)
Dec  6 14:07:16 dvb vdr[5354]: Streamdev: Client (HTTP) 10.0.2.2:35371
closed connection
Dec  6 14:07:16 dvb vdr[5354]: Streamdev: Closing connection to
10.0.2.2:35371
Dec  6 14:07:16 dvb vdr[5359]: Streamdev: Live streamer thread ended
(pid=5359, tid=131081)
Dec  6 14:07:16 dvb vdr[5354]: buffer stats: 42488 (1%) used
</vdr log>
(and vtp works as well)

starting vdr with -D 1: (S28.2 channels only), i get a "ERROR: thread.."
message for each channel i try. it takes more time but the channel is
streamed after all.
<vdr log>
Dec  6 14:09:31 dvb vdr[5459]: Streamdev: Accepted new client (HTTP)
10.0.2.2:35373
Dec  6 14:09:31 dvb vdr[5466]: receiver on device 2 thread started
(pid=5466, tid=163846)
Dec  6 14:09:31 dvb vdr[5467]: TS buffer on device 2 thread started
(pid=5467, tid=180231)
Dec  6 14:09:34 dvb vdr[5459]: ERROR: thread 163846 won't end (waited
3 seconds) - cancelling it...
Dec  6 14:09:34 dvb vdr[5468]: receiver on device 2 thread started
(pid=5468, tid=196614)
Dec  6 14:09:34 dvb vdr[5469]: Streamdev: Live streamer thread started
(pid=5469, tid=213000)
Dec  6 14:09:34 dvb vdr[5467]: TS buffer on device 2 thread ended
(pid=5467, tid=180231)
Dec  6 14:09:34 dvb vdr[5468]: buffer stats: 6204 (0%) used
Dec  6 14:09:34 dvb vdr[5470]: TS buffer on device 2 thread started
(pid=5470, tid=229383)
Dec  6 14:09:36 dvb vdr[5459]: Streamdev: Client (HTTP) 10.0.2.2:35373
closed connection
Dec  6 14:09:36 dvb vdr[5459]: Streamdev: Closing connection to
10.0.2.2:35373
Dec  6 14:09:36 dvb vdr[5470]: TS buffer on device 2 thread ended
(pid=5470, tid=229383)
Dec  6 14:09:36 dvb vdr[5468]: buffer stats: 50572 (2%) used
Dec  6 14:09:36 dvb vdr[5468]: receiver on device 2 thread ended
(pid=5468, tid=196614)
Dec  6 14:09:36 dvb vdr[5469]: Streamdev: Live streamer thread ended
(pid=5469, tid=213000)
Dec  6 14:09:36 dvb vdr[5459]: buffer stats: 50948 (1%) used
</vdr log>
(vtp doesn't work => same errors but nothing is streamed, might be vtp
client's fault as well)

starting without -D:
 for S28.E channels vdr uses the 2nd card, i get the error but the
  channel is streamed after all
<vdr log>
Dec  6 14:26:29 dvb vdr[5701]: Streamdev: Accepted new client (HTTP)
 10.0.2.2:35401
Dec  6 14:26:30 dvb vdr[5703]: receiver on device 2 thread started
 (pid=5703, tid=114696)
Dec  6 14:26:30 dvb vdr[5704]: TS buffer on device 2 thread started
 (pid=5704, tid=131081)
Dec  6 14:26:32 dvb vdr[5701]: ERROR: thread 114696 won't end (waited
 3 seconds) - cancelling it...
Dec  6 14:26:32 dvb vdr[5705]: receiver on device 2 thread started
 (pid=5705, tid=147464)
Dec  6 14:26:32 dvb vdr[5706]: Streamdev: Live streamer thread started
 (pid=5706, tid=163850)
Dec  6 14:26:32 dvb vdr[5704]: TS buffer on device 2 thread ended
 (pid=5704, tid=131081)
Dec  6 14:26:32 dvb vdr[5705]: buffer stats: 6956 (0%) used
Dec  6 14:26:32 dvb vdr[5707]: TS buffer on device 2 thread started
 (pid=5707, tid=180233)
Dec  6 14:26:34 dvb vdr[5701]: Streamdev: Client (HTTP) 10.0.2.2:35401
 closed connection
Dec  6 14:26:34 dvb vdr[5701]: Streamdev: Closing connection to
 10.0.2.2:35401
Dec  6 14:26:34 dvb vdr[5707]: TS buffer on device 2 thread ended
 (pid=5707, tid=180233)
Dec  6 14:26:34 dvb vdr[5705]: buffer stats: 64296 (3%) used
Dec  6 14:26:34 dvb vdr[5705]: receiver on device 2 thread ended
 (pid=5705, tid=147464)
Dec  6 14:26:34 dvb vdr[5706]: Streamdev: Live streamer thread ended
 (pid=5706, tid=163850)
Dec  6 14:26:34 dvb vdr[5701]: buffer stats: 64672 (2%) used
</vdr log>

 for S19.2E channels vdr uses the first card (without the sourcecap
  patch it tries to use the 2nd one but there's no S19.2E on the 2nd
  card): i get the thread error and nothing is streamed at all.
<vdr log>
Dec  6 14:28:17 dvb vdr[5701]: Streamdev: Accepted new client (HTTP)
  10.0.2.2:35403
Dec  6 14:28:17 dvb vdr[5708]: receiver on device 1 thread started
  (pid=5708, tid=196616)
Dec  6 14:28:17 dvb vdr[5709]: TS buffer on device 1 thread started
  (pid=5709, tid=213001)
Dec  6 14:28:18 dvb vdr[5693]: switching to channel 1
Dec  6 14:28:20 dvb vdr[5701]: ERROR: thread 196616 won't end (waited
  3 seconds) - cancelling it...
Dec  6 14:28:20 dvb vdr[5710]: receiver on device 1 thread started
  (pid=5710, tid=229384)
Dec  6 14:28:20 dvb vdr[5711]: Streamdev: Live streamer thread started
  (pid=5711, tid=245770)
Dec  6 14:28:20 dvb vdr[5709]: TS buffer on device 1 thread ended
  (pid=5709, tid=213001)
Dec  6 14:28:20 dvb vdr[5710]: buffer stats: 0 (0%) used
Dec  6 14:28:20 dvb vdr[5712]: TS buffer on device 1 thread started
  (pid=5712, tid=262153)
</vdr log>

strange isn't it ?

I'm going to test what happens with the budget card being the first
one.


-- 




Home | Main Index | Thread Index