[linux-dvb] Lost lock problems over extended periods of time

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

 



Dominique Dumont wrote:
> Manu Abraham <manu@xxxxxxxxxxx> writes:
> 
>>What i was wondering (a wild thought) was that, is something
>>disturbing the frontend settings once it is set up ? That was the only
>>way that a lock could be lost on the Twinhan cards, since i cannot
>>logically think of any other reason that's what written to a register
>>is lost. But that's too wild a thought.
>>
>>Dominique had a similar problem, but that was triggered off at a
>>certain period of time nearing midnight on TPS, but could be something
>>else too... Maybe he can test the same on the Twinhan DST-CI and see
>>what's the effect..
> 
> In fact, when I tune my twinhan card, I do a 'szap szap -r -x ...'.
> 
> Which means that the thead created in the function patched by Andrew
> (dvb_frontend_thread) is no longer active (I've verified this by
> adding traces to the dvb_frontend_thread state machine):
> 
> Jun  8 15:06:55 gandalf kernel: dvb_frontend_thread: retune state
> Jun  8 15:06:55 gandalf kernel: dvb_frontend_thread: retune -> tuning fast
> Jun  8 15:06:56 gandalf kernel: dvb_frontend_thread: waiting_for_lock -> tuned
> Jun  8 15:06:57 gandalf kernel: dvb_frontend_thread: tuned
> Jun  8 15:06:58 gandalf kernel: dvb_frontend_thread: tuned
> Jun  8 15:06:58 gandalf kernel: dvb_frontend_thread: tuned
> Jun  8 15:06:58 gandalf kernel: dvb_frontend_thread: tuned
> Jun  8 15:06:58 gandalf kernel: dvb_frontend_thread: tuned
> Jun  8 15:06:58 gandalf kernel: dvb_frontend_thread: tuned
> Jun  8 15:06:59 gandalf kernel: dvb_frontend_thread: tuned
> Jun  8 15:06:59 gandalf kernel: dvb_frontend_thread: tuned
> Jun  8 15:07:00 gandalf kernel: dvb_frontend_thread: tuned
> Jun  8 15:07:01 gandalf kernel: dvb_frontend_thread: tuned
> Jun  8 15:07:01 gandalf kernel: dvb_frontend_thread: exiting
> 
> Besides, when decryption fails, data is still flowing from the dvb
> card so I don't think that a lock problem triggers the decryption
> failure.

In your case, the failure might be totally different, but i thought it 
would be better to make sure..

 From your logs, it surely looks different .. So that might be some 
disturbance on the transmission at some period of time. :-(



Manu




[Index of Archives]     [Linux Media]     [Video 4 Linux]     [Asterisk]     [Samba]     [Xorg]     [Xfree86]     [Linux USB]

  Powered by Linux