VDR maintenance patch 1.4.1-5 is now available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-5.diff
This is a 'diff' against version 1.4.1-4 (which is the official version 1.4.1, patched with ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-1.diff, ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-2.diff, ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-3.diff and ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-4.diff).
Small fixes to the officially released VDR versions will be first made available as "maintenance patches" in the Developer directory, so that they can be reviewed and tested before a new official release is published.
So please apply the above patch and report whether it works (or if it causes any new problems).
Originally I wanted to release an official 1.4.2 today, but then a few things came up that I also wanted to go into the new version. Now hopefully this version will prove stable and can be officially released next sunday ;-)
The changes since version 1.4.1-4:
- Replaced the "quick workaround for additional live audio PIDs" in cDvbDevice::SetChannelDevice() with an actual solution in cDvbDevice::SetAudioTrackDevice() in order to prevent sticky PIDs in CAMs, which caused long switching times or completely blank screens when switching between encrypted channels on the same transponder (reported by Tomas Berglund). - Adapted cThread::ThreadId() to recent kernels (thanks to Ville Skyttä). - Added --remove-destination to the 'cp' command for binaries in the Makefile to avoid a crash in case a new version is installed on a running system (suggested by Petri Hintukainen). - Fixed handling "Ca Info" in case the CAM sends this again if the smart card is replaced with a different one.
Have fun!
Klaus
I have been running vdr 1.4 version with rather good success for some time now, but now all of a sudden I have started getting almost continuous restarting of vdr.
In system log I get only this: Aug 23 09:31:11 sempron vdr: [16318] ERROR: video data stream broken Aug 23 09:31:11 sempron vdr: [16318] initiating emergency exit Aug 23 09:31:12 sempron vdr: [16278] emergency exit requested - shutting down Aug 23 09:31:12 sempron lircd-0.8.0[5959]: removed client Aug 23 09:31:14 sempron vdr: [16278] emergency exit! Aug 23 09:31:15 sempron vdrwatchdog[16327]: initializing full VDR restart
I have the system running now with log level 3 which perhaps gives more information. Any quick suggestions on this problem?
I have tried already setting EPG updates to setting 0 which was suggested on one web page, but it didn't seem to help me. Program still keeps crashing on recording starts and endings. Also it keeps saying that VPS recording caused this restart even though none of my recording are set to use VPS.
System information (relevant bits of gentoo info and other): Portage 2.1-r2 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r4, 2.6.17.4 i686) ================================================================= System uname: 2.6.17.4 i686 AMD Sempron(tm) 2500+ CFLAGS="-march=athlon-xp -msse -mmmx -m3dnow -Os -fomit-frame-pointer -frerun-loop-opt -pipe" CHOST="i686-pc-linux-gnu"
Cards in machine are: # lspci -v -s 0a.0 00:0a.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Technotrend/Hauppauge DVB card rev2.1 Flags: bus master, medium devsel, latency 32, IRQ 12 Memory at dfffbe00 (32-bit, non-prefetchable) [size=512]
sempron ~ # lspci -v -s 0d.0 00:0d.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Technotrend/Hauppauge DVB card rev2.1 Flags: bus master, medium devsel, latency 32, IRQ 10 Memory at dfffbc00 (32-bit, non-prefetchable) [size=512]
Gentoo package version of vdr is media-video/vdr-1.4.1-r2 and only use flag for it is subtitles.
Hope someone has a suggestion. Here is a log level 3 messages output while software dies: Aug 23 10:01:08 sempron vdr: [19710] ERROR: video data stream broken Aug 23 10:01:08 sempron vdr: [19710] initiating emergency exit Aug 23 10:01:08 sempron vdr: [19670] emergency exit requested - shutting down Aug 23 10:01:08 sempron vdr: [19670] stopping plugin: mplayer Aug 23 10:01:08 sempron vdr: [19670] stopping plugin: screenshot Aug 23 10:01:08 sempron vdr: [19670] stopping plugin: timeline Aug 23 10:01:08 sempron vdr: [19670] stopping plugin: femon Aug 23 10:01:08 sempron vdr: [19670] stopping plugin: osdteletext Aug 23 10:01:08 sempron vdr: [19670] stopping plugin: subtitles Aug 23 10:01:08 sempron vdr: [19711] recording thread ended (pid=19711, tid=19711) Aug 23 10:01:08 sempron vdr: [19713] TS buffer on device 2 thread ended (pid=19713, tid=19713) Aug 23 10:01:08 sempron vdr: [19712] buffer stats: 87796 (4%) used Aug 23 10:01:08 sempron vdr: [19712] receiver on device 2 thread ended (pid=19712, tid=19712) Aug 23 10:01:08 sempron vdr: [19710] file writer thread ended (pid=19710, tid=19710) Aug 23 10:01:08 sempron vdr: [19670] buffer stats: 88172 (1%) used Aug 23 10:01:08 sempron vdr: [19670] timer 1 (1 0913-1016 'Puutarhaetsivät') stop Aug 23 10:01:08 sempron vdr: [19670] executing '/usr/share/vdr/bin/vdrrecord-gate.sh after "/video/Puutarhaetsivät/2006-08-23.09.13.50.99.rec"' Aug 23 10:01:08 sempron vdr: [19670] saved setup to /video/vdr/setup.conf Aug 23 10:01:08 sempron vdr: [19691] tuner on device 1 thread ended (pid=19691, tid=19691) Aug 23 10:01:08 sempron lircd-0.8.0[5959]: removed client Aug 23 10:01:08 sempron vdr: [19698] receiver on device 1 thread ended (pid=19698, tid=19698) Aug 23 10:01:08 sempron vdr: [19692] section handler thread ended (pid=19692, tid=19692) Aug 23 10:01:09 sempron vdr: [19694] tuner on device 2 thread ended (pid=19694, tid=19694) Aug 23 10:01:09 sempron vdr: [19695] section handler thread ended (pid=19695, tid=19695) Aug 23 10:01:09 sempron vdr: [19670] deleting plugin: mplayer Aug 23 10:01:09 sempron vdr: [19670] deleting plugin: screenshot Aug 23 10:01:09 sempron vdr: [19670] deleting plugin: timeline Aug 23 10:01:09 sempron vdr: [19670] deleting plugin: femon Aug 23 10:01:09 sempron vdr: [19670] deleting plugin: osdteletext Aug 23 10:01:09 sempron vdr: [19670] buffer stats: 0 (0%) used Aug 23 10:01:09 sempron vdr: [19670] deleting plugin: subtitles Aug 23 10:01:09 sempron vdr: [19670] ===================== Aug 23 10:01:09 sempron vdr: [19670] EPG bugfix statistics Aug 23 10:01:09 sempron vdr: [19670] ===================== Aug 23 10:01:09 sempron vdr: [19670] IF SOMEBODY WHO IS IN CHARGE OF THE EPG DATA FOR ONE OF THE LISTED Aug 23 10:01:09 sempron vdr: [19670] CHANNELS READS THIS: PLEASE TAKE A LOOK AT THE FUNCTION cEvent::FixEpgBugs() Aug 23 10:01:09 sempron vdr: [19670] IN VDR/epg.c TO LEARN WHAT'S WRONG WITH YOUR DATA, AND FIX IT! Aug 23 10:01:09 sempron vdr: [19670] ===================== Aug 23 10:01:09 sempron vdr: [19670] Fix Hits Channels Aug 23 10:01:09 sempron vdr: [19670] 6 18 YLE FST, Nelonen, YLE24, YLEQ, YLE TV2 Aug 23 10:01:09 sempron vdr: [19670] 7 659 SubTV, YLE FST, Nelonen, MTV3, Urheilukanava, MTV3+, YLE24, YLE Teema, YLE TV1, ... Aug 23 10:01:09 sempron vdr: [19670] 12 69 MTV3+, YLE FST, Urheilukanava, YLE24, YLE TV1 Aug 23 10:01:09 sempron vdr: [19670] ===================== Aug 23 10:01:09 sempron vdr: [19670] max. latency time 1 seconds Aug 23 10:01:09 sempron vdr: [19670] exiting Aug 23 10:01:09 sempron vdr: [19670] emergency exit! Aug 23 10:01:15 sempron vdrwatchdog[19719]: initializing full VDR restart
-Jukka
Jukka Palko wrote:
I have been running vdr 1.4 version with rather good success for some time now, but now all of a sudden I have started getting almost continuous restarting of vdr.
Aug 23 09:31:11 sempron vdr: [16318] ERROR: video data stream broken
Cards in machine are: # lspci -v -s 0a.0 00:0a.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Technotrend/Hauppauge DVB card rev2.1
sempron ~ # lspci -v -s 0d.0 00:0d.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Technotrend/Hauppauge DVB card rev2.1
Did you check that its not just the second card that has failures? For example, try switching live view to the second card using femon, or start VDR with -D 1 -D 0 to use the second card as primary.
Cheers,
Udo
Udo Richter wrote:
Jukka Palko wrote:
I have been running vdr 1.4 version with rather good success for some time now, but now all of a sudden I have started getting almost continuous restarting of vdr.
Aug 23 09:31:11 sempron vdr: [16318] ERROR: video data stream broken
Cards in machine are: # lspci -v -s 0a.0 00:0a.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Technotrend/Hauppauge DVB card rev2.1
sempron ~ # lspci -v -s 0d.0 00:0d.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Technotrend/Hauppauge DVB card rev2.1
Did you check that its not just the second card that has failures? For example, try switching live view to the second card using femon, or start VDR with -D 1 -D 0 to use the second card as primary.
I doublechecked things on the host a while back and looks like the cause is clock adjustment. :) After disabling the adjustment from transmissions, the continuous restarting ended. Propably ain't got the priviledges set up properly. ;)
Aug 23 10:00:32 sempron vdr: [19692] System Time = Wed Aug 23 10:00:32 2006 (1156316432) Aug 23 10:00:32 sempron vdr: [19692] Local Time = Wed Aug 23 10:01:08 2006 (1156316468) Aug 23 10:01:08 sempron vdr: [19710] ERROR: video data stream broken Aug 23 10:01:08 sempron vdr: [19710] initiating emergency exit Aug 23 10:01:08 sempron vdr: [19670] emergency exit requested - shutting down
Thanks for the suggestion still.
-Jukka
Jukka Palko wrote:
I doublechecked things on the host a while back and looks like the cause is clock adjustment. :) After disabling the adjustment from transmissions, the continuous restarting ended. Propably ain't got the priviledges set up properly. ;)
Aug 23 10:00:32 sempron vdr: [19692] System Time = Wed Aug 23 10:00:32 2006 (1156316432) Aug 23 10:00:32 sempron vdr: [19692] Local Time = Wed Aug 23 10:01:08 2006 (1156316468) Aug 23 10:01:08 sempron vdr: [19710] ERROR: video data stream broken
Well, thats an important hint!
Actually, it looks like the VDSB detection is not secured for clock adjustment. Time jumped forward 36 seconds (see log time index), and because of that VDR did not see useful data for more than 30 seconds, and did a VDSB...
Question is, why did such a rather big time adjustment happen just while recording, and not before the recording started.
Did you set up time adjustment on a specific channel, and did you record from this channel/transponder? How frequent are these time adjustments? Does your clock do massive drifting when not syncing with the sat time?
Cheers,
Udo
Udo Richter wrote:
Jukka Palko wrote:
I doublechecked things on the host a while back and looks like the cause is clock adjustment. :) After disabling the adjustment from transmissions, the continuous restarting ended. Propably ain't got the priviledges set up properly. ;)
Aug 23 10:00:32 sempron vdr: [19692] System Time = Wed Aug 23 10:00:32 2006 (1156316432) Aug 23 10:00:32 sempron vdr: [19692] Local Time = Wed Aug 23 10:01:08 2006 (1156316468) Aug 23 10:01:08 sempron vdr: [19710] ERROR: video data stream broken
Well, thats an important hint!
Actually, it looks like the VDSB detection is not secured for clock adjustment. Time jumped forward 36 seconds (see log time index), and because of that VDR did not see useful data for more than 30 seconds, and did a VDSB...
Question is, why did such a rather big time adjustment happen just while recording, and not before the recording started.
Did you set up time adjustment on a specific channel, and did you record from this channel/transponder? How frequent are these time adjustments? Does your clock do massive drifting when not syncing with the sat time?
It can have been from the fact that my system has usually used ntp time updates and I had vdr time adjustment on just for testing purposes and forgot it on. ;)
Possibly the ntp time is way off from the channel times? Wouldn't be surprising imho.
Looks like I setup my log rotation to keep quite a clean schedule on the host and previous restarts informations have gotten the /dev/null treatment. So I can't get that info back right now and I would prefer not to change it back to previous setting until during weekend when I can do testing without getting complaints from other viewers of the channels. ;)
Looks like yesterday evenings restart while recording started produced different issues: Aug 23 18:33:04 sempron vdr: [20478] switching device 2 to channel 1 Aug 23 18:34:00 sempron vdr: [20478] switching device 2 to channel 1 Aug 23 18:34:00 sempron vdr: [20478] timer 15 (1 1834-1916 'Luontohetki: Vedenalaiset kodit') start Aug 23 18:34:00 sempron vdr: [20478] Title: 'Luontohetki: Vedenalaiset kodit' Subtitle: '(null)' Aug 23 18:34:00 sempron vdr: [20478] executing '/usr/share/vdr/bin/vdrrecord-gate.sh before "/video/Luontohetki:_Vedenalaiset_kodit/2006-08-23.18.34.50.99. rec"' Aug 23 18:34:00 sempron vdr: [20478] record /video/Luontohetki:_Vedenalaiset_kodit/2006-08-23.18.34.50.99.rec Aug 23 18:34:00 sempron vdr: [20478] creating directory /video/Luontohetki:_Vedenalaiset_kodit Aug 23 18:34:00 sempron vdr: [20478] creating directory /video/Luontohetki:_Vedenalaiset_kodit/2006-08-23.18.34.50.99.rec Aug 23 18:34:00 sempron vdr: [20478] recording to '/video/Luontohetki:_Vedenalaiset_kodit/2006-08-23.18.34.50.99.rec/001.vdr' Aug 23 18:34:00 sempron vdr: [30790] file writer thread started (pid=30790, tid=30790) Aug 23 18:34:00 sempron vdr: [30791] recording thread started (pid=30791, tid=30791) Aug 23 18:34:00 sempron vdr: [30792] receiver on device 2 thread started (pid=30792, tid=30792) Aug 23 18:34:00 sempron vdr: [30793] TS buffer on device 2 thread started (pid=30793, tid=30793) Aug 23 18:34:01 sempron vdr: [30791] cVideoRepacker: found system start code: stream seems to be scrambled or not demultiplexed Aug 23 18:34:01 sempron vdr: [30791] cAudioRepacker(0xC0): skipped 944 bytes while syncing on next audio frame Aug 23 18:34:01 sempron vdr: [30790] ERROR: unknown picture type '6' Aug 23 18:34:01 sempron vdr: [30790] ERROR: unknown picture type '6' Aug 23 18:34:02 sempron vdr: [30790] ERROR: unknown picture type '6' Aug 23 18:34:03 sempron vdr: [30790] ERROR: unknown picture type '5' Aug 23 18:34:05 sempron vdr: [30790] ERROR: unknown picture type '4' Aug 23 18:34:05 sempron vdr: [30790] ERROR: unknown picture type '6' Aug 23 18:34:05 sempron vdr: [30790] ERROR: unknown picture type '4' Aug 23 18:34:05 sempron vdr: [30790] ERROR: unknown picture type '6' Aug 23 18:34:05 sempron vdr: [30790] ERROR: unknown picture type '4' Aug 23 18:34:05 sempron vdr: [30790] ERROR: unknown picture type '4' Aug 23 18:34:06 sempron vdr: [30790] ERROR: unknown picture type '6' Aug 23 18:34:06 sempron vdr: [30790] initiating emergency exit Aug 23 18:34:06 sempron vdr: [20478] emergency exit requested - shutting down
-Jukka
-
Jukka Palko -
Klaus Schmidinger -
Udo Richter