[vdr] Re: VDR crashes during record

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

Alexander Reitinger wrote:
> 
> im new to vdr but this can't be normal
> 
> vdr works fine , but it randomly crashes while recording, up to 0-3/5 times
> in a hour,
> the log files don't show anything weired ( see below , log file during a
> crash )
> the best at it, it seems to happen only on RTL2 , i recorded another channel
> (MTV), 2 hours and no crash ( luck ??)
> Replaying/Cutting the (incomplete) recordings works fine, so whats wrong ?
> maybe wrong system configuration  ( 2.4.17 ,  pII300 ,
> siemens_dvb-0.9.4-2002-04-01 , vdr-1.0.0 ) ??
> i need to do more test , but how can i obtain more information when vdr
> crashes ?
> 
> thanks
> alex
> 
> --cut--
> Apr 18 19:40:13 zardoz vdr[1333]: VDR version 1.0.0 started
> Apr 18 19:40:13 zardoz vdr[1333]: loading /video/setup.conf
> Apr 18 19:40:13 zardoz vdr[1333]: loading /video/channels.conf
> Apr 18 19:40:13 zardoz vdr[1333]: loading /video/timers.conf
> Apr 18 19:40:13 zardoz vdr[1333]: loading /video/commands.conf
> Apr 18 19:40:13 zardoz vdr[1333]: loading /video/svdrphosts.conf
> Apr 18 19:40:13 zardoz vdr[1333]: loading /video/ca.conf
> Apr 18 19:40:13 zardoz vdr[1333]: probing /dev/ost/frontend0
> Apr 18 19:40:13 zardoz vdr[1333]: probing /dev/ost/frontend1
> Apr 18 19:40:13 zardoz vdr[1333]: found 1 video device
> Apr 18 19:40:13 zardoz vdr[1333]: setting primary DVB to 1
> Apr 18 19:40:13 zardoz vdr[1333]: reading EPG data from /video/epg.data
> Apr 18 19:40:13 zardoz vdr[1335]: EIT processing thread started (pid=1335) - master
> Apr 18 19:40:14 zardoz vdr[1333]: switching to channel 4
> Apr 18 19:40:14 zardoz vdr[1336]: LIRC remote control thread started (pid=1336)
> Apr 18 19:40:14 zardoz vdr[1333]: SVDRP listening on port 2001
> Apr 18 19:40:14 zardoz vdr[1333]: setting watchdog timer to 60 seconds
> Apr 18 19:40:19 zardoz vdr[1333]: timer 2 start
> Apr 18 19:40:19 zardoz vdr[1333]: switching to channel 4
> Apr 18 19:40:19 zardoz vdr[1333]: Title: 'Dragon Ball Z' Subtitle: ''
> Apr 18 19:40:19 zardoz vdr[1333]: record /video/@Dragon_Ball_Z__/2002-04-18.19:02.50.50.rec
> Apr 18 19:40:19 zardoz vdr[1333]: recording to '/video/@Dragon_Ball_Z__/2002-04-18.19:02.50.50.rec/004.vdr'
> Apr 18 19:40:19 zardoz vdr[1340]: output thread started (pid=1340)
> Apr 18 19:40:19 zardoz vdr[1341]: input thread started (pid=1341)
> Apr 18 19:40:20 zardoz vdr[1333]: max. latency time 1 seconds
> Apr 18 19:44:44 zardoz vdr[1333]: max. latency time 2 seconds
> Apr 18 19:45:06 zardoz vdr[1333]: max. latency time 5 seconds

Apparently it was not interrupted by any signal, otherwise there would have to be
a line "caught signal..." here.

> Apr 18 19:51:15 zardoz vdr[1333]: saved setup to /video/setup.conf
> Apr 18 19:51:15 zardoz vdr[1333]: =====================
> Apr 18 19:51:15 zardoz vdr[1333]: EPG bugfix statistics
> Apr 18 19:51:15 zardoz vdr[1333]: =====================
> Apr 18 19:51:15 zardoz vdr[1333]: IF SOMEBODY WHO IS IN CHARGE OF THE EPG DATA FOR ONE OF THE LISTED
> Apr 18 19:51:15 zardoz vdr[1333]: CHANNELS READS THIS: PLEASE TAKE A LOOK AT THE FUNCTION cEventInfo::FixEpgBugs()
> Apr 18 19:51:15 zardoz vdr[1333]: IN VDR/eit.c TO LEARN WHAT'S WRONG WITH YOUR DATA, AND FIX IT!
> Apr 18 19:51:15 zardoz vdr[1333]: =====================
> Apr 18 19:51:15 zardoz vdr[1333]: Fix^IHits^IChannels
> Apr 18 19:51:15 zardoz vdr[1333]: 0^I1973^IVOX
> Apr 18 19:51:15 zardoz vdr[1333]: 1^I1247^IVOX
> Apr 18 19:51:15 zardoz vdr[1333]: =====================
> Apr 18 19:51:15 zardoz vdr[1335]: EIT processing thread ended (pid=1335) - master
> Apr 18 19:51:18 zardoz vdr[1333]: buffer stats: 543696 (51%) used
> Apr 18 19:51:18 zardoz vdr[1333]: max. latency time 5 seconds
> Apr 18 19:51:18 zardoz vdr[1333]: exiting

Apparently it was not an "emergency exit", because otherwise there would be an
"emergency exit!" message here.

> Apr 18 19:51:23 zardoz kernel: Linux video capture interface: v1.00
> Apr 18 19:51:28 zardoz su[1486]: + pts/0 root-root
> Apr 18 19:51:28 zardoz vdr[1486]: VDR version 1.0.0 started
> Apr 18 19:51:28 zardoz vdr[1486]: loading /video/setup.conf
> Apr 18 19:51:28 zardoz vdr[1486]: loading /video/channels.conf
> Apr 18 19:51:28 zardoz vdr[1486]: loading /video/timers.conf
> ------  cut ------

Well, since it was neither a signal nor an emergency exit, and the only two conditions
where the main 'while' loop would be left are either 'Interrupted' becoming !=0 (which
apparently didn't happen because otherwise there would be a "caught signal..." message)
or the 'break' statement in the "Handle emergency exits" section right at the beginning
of the loop (which apprently also didn't happen since there was no such message, either),
I'm afraid I have no idea why this could have happened.

Just for clarity: is this plain vanilla VDR 1.0.0, or have you modified
the source in any way?

Klaus
-- 
_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10
CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
Hofmark 2                               Email:   kls@cadsoft.de
D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de
_______________________________________________________________