[vdr] Re: Broken stream detection (again)

[Juri Haberland <juri@koschikode.com>]

Peter Dittmann wrote:
> On Thu, 12 Jun 2003, you wrote:

>> So I assume you told VDR to set the system time from a transponder?
> 
> Yes, but I disabled this today evening and the glitches are still there. They
> are more or less precize 72min +/- 30sec (to precize to be concidence !)
> And they correct automaticly in the next log entry without VDR now kicking in
> (with enabled time setting VDR was kicking in to fix the system time).
> If you read carefully: according log it was not VDR that caused this offset,
> but VDR was fixing it !
> I'm absolutely shure no other service is running that set/tweak
> system time on this system.
> To me this locks like a race condition, e.g. checking time at a critical time
> window that caused some temporary overflow.
> (by the way 2^32usec are 71min 34,9673sec and timer.c counts usec's;
> strange coincidence ;-) )

What kind of hardware do you have? This sounds very unusual and I think
you should take this to the kernel developers at
linux-kernel@vger.kernel.org.

>>> I was just pointing towards there are several people complaining
>>> about LIRC time problems, some complain about glitches in
>>> recordings (which I have now as of timers being continously
>>> stopped and restarted), a lot are complaining about emergency
>>> exits.
>> 
>> These seem to be different problems, but if your time jumps (for whatever
>> reason), than all kind of things may break - not only VDR.
> 
> Shure ??!

Yes. People have problems with "emergency Exits" because the receiption
on the cards get bad due to rain and therefore VDR restarts. Most
glitches in recordings were due tu bugs in the driver/firmware.

> The LIRC problem (IEEE: your clock just jumped backward) seems to be a
> problem with do_fast_gettimeoffset() in time.c. I have spend a few time on this
> with the old setup using Suse7.1/2.4.0; and I have counted at least 3..4
> postings over the last 6 month that mentioned this.

Lirc problems often (but not always) happen, because people run
rdate/ntpdate.

> The problems I still have with timers starting/stopping at random produces the
> glitches reported by different persons in the list. The log entries are only
> visible when VDR is told to do full logging (which is not the default !). So a

According to Klaus Schmidinger and the output of 'vdr -h' VDR *does* runs
with maximum logging by default.

Actually, I have the feeling that you are barking up the wrong tree - but
it's just a feeling.

Cheers,
Juri



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.