syphyr@xxxxxxxxx(C.Y.M) 22.05.05 13:05
>Mika Lehtinen wrote:
>> Hi,
>>
>> I have encountered similar behaviour. My setup is:
>>
>> 1.3.24
>> 2.4.26 kernel
>> linuxtv-dvb-1.1.1
>> Two TT DVB-C cards (one FF, one Budget)
>>
>> May 22 19:59:00 play vdr[3538]: timer 9 (7 1959-2102 'Maison Bing ja
>> Art Nouveau') start
>> May 22 19:59:00 play vdr[3538]: record
>> /video/Maison_Bing_ja_Art_Nouveau/2005-05-22.19:59.50.99.rec
>> May 22 19:59:32 play vdr[3551]: ERROR: video data stream broken
>> May 22 19:59:32 play vdr[3551]: initiating emergency exit
>>
>> It is interesting to see, that I too have exactly 32 seconds between
>> the timer start and "ERROR: video data stream broken". Is this a
>> timer, or something?
>>
>Do you have NPTL enabled?
I don't know, but that's no issue for 2.4. kernels IIRC.
(We had that discussing 4 month back ("thread save/safe")
Doesn't VDR really not drop a line into syslog if it is
running under NPTL or not?
That seems to be very very important to know.
>I have the same problem if I enable NPTL.
>NPTL works fine, except, after vdr has been running for a few hours,
>and a timer goes off, thats what causes the VDSB. It seems that NPTL
>and timers dont work well with eachother.
I had run 1.3.18 for month without any such problems.
I only changed the VDR binary, nothing else.
(I copied "my" runvdr)
OK, i upgraded OSD-teletext to 0.5, but i assume taht should
not matter.
The "responsiveness" of VDR to LIRC keys is signifcantly better,
but sometimes it still hangs. (I'll note when).
