[vdr] Re: stream broken w. 1.3.18

[Rainer Zocholl <UseNet-Posting-Nospam-74308-@zocki.toppoint.de>]

UseNet-Posting-Nospam-74308-@zocki.toppoint.de(Rainer Zocholl)  14.01.05 17:01


>With 1.3.18 there are again problems with "budget" cards.

>i have 3 DVB-FF 1.5/2.1 and one DVB-T AverMedia 771
>recently i recorded one sat channel (ESA ;-) )
>and tried to watch other programs on the DVB-T card.
>Every some 10sec a noticed a drop an found an emergy exit in
>vdr logfile.

>Too i recently mailed that multicordings failed.

That's no problem of "budget" cards, it happens with FF too.

First VDR should record 3 timer:
emergency exit...

Then one of timers were done and vdr should record 2 channels 
of the "higher" cards. 
I still got two "stream broken" and VDR exits,
as VDR seems to continue to use the same hi cards...

Manually rmmod.ing all modules and reloading "solved" the problem.


As i used the linuxtv-dvb-1.1.1 (because of DVB-T support) 
the "unload" of the drivers via "Makefile" by runvdr does not work!
That leads to the endless emergency loop that made the
problem so obvious.


But:
I assume that problem is occuring far more often than here reported!
On the first, 3 recordings at a time might go away
very soon, as that are only overlapping timers.
On the other hand, the "skips" caused by the exits are not very obvious 
in the recordings.
So the user will see only some few "dropouts" at the beginning
of a recordings.

So:
Why did it work with (threadpatched)1.3.17 flawlessly and 
does not anymore with 1.3.18?
What was not migrated from 1.3.17 to 1.3.18?
Could it be the thread.c module?





Rainer---<=====>                         Vertraulich
             //
           //                              
         <=====>--------------ocholl, Kiel, Germany ------------