[linux-dvb] FE_HAS_LOCK spikes with Skystar2

[Wolfgang Fritz <wolfgang.fritz@gmx.net>]

Hello,

during my debugging of the VDR "video data stream broken" error I've
found that my skystar2 delivers short "FE_HAS_LOCK" events on channels it
can not tune to. I modified VDR to read frontend events with poll() and
dump them to syslog with timing information (time difference between
events) and got the following:

Jul 25 20:34:27 vdr vdr[4099]: SetChannelDevice: channel 585, LiveView=0
Jul 25 20:34:28 vdr vdr[4099]: Frontend 1 tuning to channel Free-X TV
Jul 25 20:34:28 vdr vdr[4125]: Event on frontend 1 (channel Free-X TV): 00 (#1) dt = 22230 ms

****** See the FE_HAS_LOCK spike below ***********
Jul 25 20:34:28 vdr vdr[4125]: Event on frontend 1 (channel Free-X TV): 1f (#2) dt =    0 ms
Jul 25 20:34:28 vdr vdr[4125]: Event on frontend 1 (channel Free-X TV): 00 (#1) dt =  100 ms
Jul 25 20:34:28 vdr vdr[4125]: Event on frontend 1 (channel Free-X TV): 02 (#1) dt =  200 ms
Jul 25 20:34:28 vdr vdr[4125]: Event on frontend 1 (channel Free-X TV): 00 (#1) dt =  100 ms
Jul 25 20:34:29 vdr vdr[4125]: Event on frontend 1 (channel Free-X TV): 02 (#1) dt =  800 ms
..
This continues until VDR switches to another channel.
No other FE_HAS_LOCK events were received. If VDR tries to tune to thius channel again,
the spike appears again.

I'm running a Skystar2 rev 2.6c with the 2.4 dvb-kernel.

Question: Must an application be able to handle such a situation or is it a driver bug?

Wolfgang