[linux-dvb] Timer starts late...

[Marcus Kuba <marcus@kuba4u.de>]

Hi all... hi Klaus,

It has happened to me several times now that a timer does not start at 
the programmed time:

Aug 22 02:41:49 vdr -- MARK --
Aug 22 02:46:41 vdr vdr[5133]: System Time = Wed Aug 22 02:46:41 2001  
(998441201) 
Aug 22 02:46:41 vdr vdr[5133]: Local Time  = Wed Aug 22 02:46:38 2001  
(998441198) 

as we can see, the time/date of the machine was correct...

Aug 22 02:47:45 vdr kernel: dvb1: 0e 00 41 ffffffcb ffffffaf 00 A   
Aug 22 02:47:45 vdr kernel: dvb1: 0c 00 09 06 2e 00 76 ffffffe5 00 00 00 
02 2e 08 53 ffffffc0 00 00 00 ffffff90 00 00 00 00 2e 08 54 50 2e 00 41 
ffffff8f   . v     . S

I will leave these CAM-debug-lines out below, no other lines will be 
deleted.

Aug 22 02:59:00 vdr /USR/SBIN/CRON[5789]: (root) CMD ( rm -f 
/var/spool/cron/lastrun/cron.hourly) 
Aug 22 03:21:46 vdr -- MARK --
Aug 22 03:41:46 vdr -- MARK --
Aug 22 03:59:00 vdr /USR/SBIN/CRON[5904]: (root) CMD ( rm -f 
/var/spool/cron/lastrun/cron.hourly) 
Aug 22 03:59:43 vdr vdr[5130]: timer 2 start

This timer was programmed to start at 03:15 !! If you look below you can 
also see that from the naming of the directories!

Aug 22 03:59:43 vdr vdr[5130]: switching to channel 22
Aug 22 03:59:44 vdr vdr[5130]: Title: 'Ein Date zu dritt' Subtitle: 
'Orderline: D: 0180-5530000 (6 DM) A: 01-49168800 (42 ATS) (Best.-Nr. 
560)'
Aug 22 03:59:44 vdr vdr[5130]: record 
/video0/Ein_Date_zu_dritt/2001-08-22.03:15.50.99.rec
Aug 22 03:59:44 vdr vdr[5130]: creating directory 
/video0/Ein_Date_zu_dritt
Aug 22 03:59:44 vdr vdr[5130]: creating directory 
/video0/Ein_Date_zu_dritt/2001-08-22.03:15.50.99.rec
Aug 22 03:59:44 vdr vdr[5130]: recording to 
'/video0/Ein_Date_zu_dritt/2001-08-22.03:15.50.99.rec/001.vdr'
Aug 22 03:59:44 vdr vdr[5130]: creating directory 
/video2/Ein_Date_zu_dritt
Aug 22 03:59:44 vdr vdr[5130]: creating directory 
/video2/Ein_Date_zu_dritt/2001-08-22.03:15.50.99.rec
Aug 22 03:59:44 vdr vdr[5912]: output thread started (pid=5912)
Aug 22 03:59:44 vdr vdr[5913]: input thread started (pid=5913)
Aug 22 04:17:53 vdr vdr[5133]: read incomplete section - seclen = 411, n 
= -1
Aug 22 04:17:53 vdr vdr[5133]: read incomplete section - seclen = 608, n 
= 213

now follow a lot of these lines, I don't think they are important here...

Aug 22 04:17:56 vdr vdr[5133]: read incomplete section - seclen = 2350, n 
= 311
Aug 22 04:17:56 vdr vdr[5133]: read incomplete section - seclen = 460, n 
= 149
Aug 22 04:17:56 vdr vdr[5133]: Received stuffing section in EIT 
Aug 22 04:17:56 vdr vdr[5133]: read incomplete section - seclen = 1385, n 
= 190
Aug 22 04:17:58 vdr vdr[5912]: recording to 
'/video0/Ein_Date_zu_dritt/2001-08-22.03:15.50.99.rec/002.vdr'
Aug 22 04:36:11 vdr vdr[5912]: recording to 
'/video0/Ein_Date_zu_dritt/2001-08-22.03:15.50.99.rec/003.vdr'
Aug 22 04:54:25 vdr vdr[5912]: recording to 
'/video0/Ein_Date_zu_dritt/2001-08-22.03:15.50.99.rec/004.vdr'
Aug 22 04:59:00 vdr /USR/SBIN/CRON[6073]: (root) CMD ( rm -f 
/var/spool/cron/lastrun/cron.hourly) 
Aug 22 05:00:00 vdr vdr[5133]: cleaning up schedules data
Aug 22 05:06:03 vdr vdr[5912]: ERROR: can't record MPEG1!

What does this say?

Aug 22 05:12:38 vdr vdr[5912]: recording to 
'/video0/Ein_Date_zu_dritt/2001-08-22.03:15.50.99.rec/005.vdr'
Aug 22 05:15:02 vdr vdr[5912]: output thread ended (pid=5912)
Aug 22 05:15:02 vdr vdr[5913]: input thread ended (pid=5913)
Aug 22 05:15:02 vdr vdr[5130]: buffer stats: 110356 (10%) used
Aug 22 05:15:02 vdr vdr[5130]: timer 2 stop
Aug 22 05:15:02 vdr vdr[5130]: deleting timer 2

Any clues?

It's a 0.92 with LCDproc and Stefans trickmode-patches, Klaus' 
0817-driver and kernel 2.4.5... needless to say that other timers (the 
same schedule 24 hours earlier for example) worked well.

I must also tell you that I have had a few timing-related problems  with 
vdr lately. After a fresh boot of the complete system, all works well... 
but after some hours of uptime, strange things happen to the OSD (no 
matter if vdr is original or patched):
when switching channels, the Info-OSD doesn't stay for five seconds as 
normal, but goes off immediately. The same happens when I just press OK. 
When I press OK repeatedly, the OSD stays... but in most cases then 
forever/until OK is pressed again.
In the replay-OSD, the time-info on the left is only updated for a short 
time and then suddenly stops.
A driver-reload/vdr-restart doesn't help... only a reboot cures this for 
a while. Interestingly, I have also compiled a 2.4.8-kernel lately and 
when I boot from that (and of course do compile driver/vdr as well), this 
behaviour is there immediately after a fresh boot.

Currently, I have no idea what's going wrong.. 

Greetings,   Marcus


--
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.