On Mon, 24 Jul 2006 09:58:00 +0200, Peter Dittmann wrote > Had another kernel crash this morning with stuck SVDRP: (...) > Jul 24 04:19:05 vdr vdr[1399]: connect from 127.0.0.1, port 32792 - accepted > Jul 24 04:19:05 vdr vdr[1399]: SVDRP message: 'Infosat:Received 1490 of 1500 > data blocks [ 99.33%]' > Jul 24 04:19:05 vdr vdr[1399]: info: Infosat:Received 1490 of 1500 data > blocks [ 99.33%] > Jul 24 04:19:05 vdr vdr[1399]: closing SVDRP connection > Jul 24 04:20:05 vdr vdr[1399]: connect from 127.0.0.1, port 32793 - accepted > Jul 24 04:20:05 vdr vdr[1399]: SVDRP message: 'Infosat:Received 1497 > of 1500 data blocks [ 99.80%]' > Jul 24 04:20:05 vdr vdr[1399]: info: Infosat:Received 1497 of 1500 > data blocks [ 99.80%] > Jul 24 04:20:05 vdr vdr[1399]: closing SVDRP connection > > >> this seems to be VDRAdin as it's not the same 60sec raster as the > messages from infosatepg > > Jul 24 04:20:41 vdr vdr[1399]: connect from 127.0.0.1, port 32794 - > accepted > > Jul 24 04:21:42 vdr vdr[1399]: PANIC: watchdog timer expired - exiting! I don't know infosatepg, but as far as I've read, it first downloads the data via DVB-S and then tvmovie2vdr uploads it to SVDRP. The whole process is controled by infosatepg.sh. According to the log, infosatepg receives about 5-10 packets per minute, so it is most likely finished at Jul 24 04:20:41. At that time the SVDRP upload starts which is simply too fast. Again: try to find out what's really happening when the watchdog is triggered. Use a sniffer, add some debug lines to vdr - whatever. Good luck, Frank
