[vdr] vdr-1.3.39: VDR extremely sluggish

Wolfgang Fritz wolfgang.fritz at gmx.net
Fri Jan 27 20:12:06 CET 2006


Klaus Schmidinger wrote:
> Wolfgang Fritz wrote:
>> Hello,
>>
>> I want to report a problem with VDR when a recording is tried while no
>> signal is available.
>>
>> Last week a small local "blizzard" covered my dish with snow so I lost
>> the sat signal.
>>
>> When VDR started a recording in this situation, its response to the RC
>> became extremely sluggish with several seconds delay between a RC key
>> press and the reaction. Whe the "recording" finally terminated, the
>> response times became normal again. The sat signal was still unavailable.
>>
>> The CPU load stayed low (nearly 0) in this situation, and no RC keys got
>> lost.
>>
>> This happened with VDR 1.3.39 with jummplay patch applied, Kernel 2.6.15
>> and v4l-dvb CVS drivers from 3.1.2006. I did not try a vanilla VDR but
>> can do this if required.
>>
>> I have attached a syslog excerpt.
>>
>> Wolfgang
>>
>>
>> ------------------------------------------------------------------------
>>
>> Jan 17 19:59:00 vdr vdr[4211]: switching device 2 to channel 3
>> Jan 17 19:59:00 vdr vdr[4211]: timer 1 (3 1959-2017 'Tagesschau') start
>> Jan 17 19:59:00 vdr vdr[4211]: Title: 'Tagesschau' Subtitle: 'Nachrichtenmagazin der ARD'
>> Jan 17 19:59:00 vdr vdr[4211]: record /video/Tagesschau/Nachrichtenmagazin_der_ARD/2006-01-17.19.59.50.10.rec
>> Jan 17 19:59:00 vdr vdr[4211]: creating directory /video/Tagesschau
>> Jan 17 19:59:00 vdr vdr[4211]: creating directory /video/Tagesschau/Nachrichtenmagazin_der_ARD
>> Jan 17 19:59:00 vdr vdr[4211]: creating directory /video/Tagesschau/Nachrichtenmagazin_der_ARD/2006-01-17.19.59.50.10.rec
>> Jan 17 19:59:00 vdr vdr[4211]: recording to '/video/Tagesschau/Nachrichtenmagazin_der_ARD/2006-01-17.19.59.50.10.rec/001.vdr'
>> Jan 17 19:59:02 vdr vdr[4211]: frontend 1 timed out while tuning to channel 3, tp 111953
>> Jan 17 19:59:05 vdr vdr[4211]: ERROR: device 2 has no lock, can't attach receiver!
> 
> Apparently you have enabled the line
> 
> //#define WAIT_FOR_TUNER_LOCK
> 
> in device.c. By default this line is not active, so if you haven't
> enabled it yourself (in which case you shouldn't be surprised by
> the behavior) I wonder which patch did so? If a patch activates
> this line, I strongly recommend the patch author refrains from
> doing so!
> 

Oops, I`ve done that on my own long time ago because it helped against
VDSB errors with my Skystar2. I will change it and see whether the
Skystar behaves better now with the current driver.

But why should this block the key processing? It's a multi threaded
application, isn't it?

Wolfgang



> Klaus

[rest snipped]
>
> _______________________________________________
> vdr mailing list
> vdr at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
> 





More information about the vdr mailing list