Re: [vdr] EIT related crash with 2.0.6
On Wed, Apr 16, 2014 at 4:37 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 14.04.2014 21:58, Ville Skyttä wrote: Hello, I'm seeing an EIT related crash of VDR 2.0.6 every now and then, no idea if there's a way to trigger it on demand somehow nor do I know when exactly it happens; I just sometimes find a core file for it. gdb backtrace attached, my VDR is quite a patched one (the one from Fedora) but the line numbers appear to make sense for vanilla 2.0.6 too. The only explanation I can think of is that some other thread is accessing the global 'Schedules' list after releasing its SchedulesLock. Are there any EPG related plugins in use? Yes, epgsearch 1.0.1beta5 and epgfixer 0.3.1. FWIW, none of the patches I have touch eit*.[hc] or epg.[hc]. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EIT related crash with 2.0.6
On 17.04.2014 09:04, Ville Skyttä wrote: On Wed, Apr 16, 2014 at 4:37 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 14.04.2014 21:58, Ville Skyttä wrote: Hello, I'm seeing an EIT related crash of VDR 2.0.6 every now and then, no idea if there's a way to trigger it on demand somehow nor do I know when exactly it happens; I just sometimes find a core file for it. gdb backtrace attached, my VDR is quite a patched one (the one from Fedora) but the line numbers appear to make sense for vanilla 2.0.6 too. The only explanation I can think of is that some other thread is accessing the global 'Schedules' list after releasing its SchedulesLock. Are there any EPG related plugins in use? Yes, epgsearch 1.0.1beta5 and epgfixer 0.3.1. FWIW, none of the patches I have touch eit*.[hc] or epg.[hc]. Well, maybe epgsearch or epgfixer is messing something up? Does the problem happen if these plugins are not in use? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] skipping 5/10 seconds
On Sun, 06 Apr 2014 21:26:08 +0200 Peter Münster pmli...@free.fr wrote: On Sun, Apr 06 2014, VDR User wrote: What I would be willing to accept is a patch that makes the skip delta of the yellow and green keys (currently a fixed +/-60s) configurable. Yes, that's fine. But what's the problem with a second skip-value for buttons 1 and 3? If the skip amount can configurable then each user can set it to his own liking and no extra buttons needed. That seems like the simplest best solution in my opinion. Can you think of any setup that actually uses several skip buttons? Skipping doesn't need to be complicated or require a handful of buttons. Allow the user to set his preferred skip+ and skip- amounts, and done deal. :) The question was What's the problem?. Do you have an answer? Of course the default setting can be no second skip-value, nothing would change for users. But for my personal setup I'll use 2 buttons for 5s-steps and 2 buttons for 60s-steps. If I could do that without patching VDR, that would be really nice. +1 for more skipping choices and making the size of the steps configurable. ludi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EIT related crash with 2.0.6
On Thu, Apr 17, 2014 at 10:56 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 17.04.2014 09:04, Ville Skyttä wrote: On Wed, Apr 16, 2014 at 4:37 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 14.04.2014 21:58, Ville Skyttä wrote: Hello, I'm seeing an EIT related crash of VDR 2.0.6 every now and then, no idea if there's a way to trigger it on demand somehow nor do I know when exactly it happens; I just sometimes find a core file for it. gdb backtrace attached, my VDR is quite a patched one (the one from Fedora) but the line numbers appear to make sense for vanilla 2.0.6 too. The only explanation I can think of is that some other thread is accessing the global 'Schedules' list after releasing its SchedulesLock. Are there any EPG related plugins in use? Yes, epgsearch 1.0.1beta5 and epgfixer 0.3.1. FWIW, none of the patches I have touch eit*.[hc] or epg.[hc]. Well, maybe epgsearch or epgfixer is messing something up? Does the problem happen if these plugins are not in use? It happens so rarely that it's most likely very hard to tell. I'll give it a shot without epgfixer but epgsearch is such an essential feature for this box that I don't think I'll be trying without it any time soon. I skimmed through both epgfixer and epgsearch sources quickly but didn't notice an obvious unlocked schedules access; it's entirely possible that I missed something though. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Invalid sat cable number errors
Hello, I see errors like the below on every VDR (2.0.6) startup and apparently exactly 30 minute intervals after that in syslog: ERROR: invalid sat cable number in '[apparent binary junk]' The binary junk varies, today it's been for example 'C0C0ۙ^?' and 'C00BEA48F^?' as shown by less. Any ideas what would be causing this or if I could do something to help debug this further? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Invalid sat cable number errors
On Thu, Apr 17, 2014 at 3:22 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 17.04.2014 13:07, Ville Skyttä wrote: Hello, I see errors like the below on every VDR (2.0.6) startup and apparently exactly 30 minute intervals after that in syslog: ERROR: invalid sat cable number in '[apparent binary junk]' The binary junk varies, today it's been for example 'C0C0ۙ^?' and 'C00BEA48F^?' as shown by less. Any ideas what would be causing this or if I could do something to help debug this further? Please post (or send me via PM) the complete log from the very start of VDR up until the above error message. Sent in PM. Please also post the line DeviceBondings = ... from your setup.conf file. # grep DeviceBondings /etc/vdr/setup.conf DeviceBondings = 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 This is a DVB-C only system BTW (one FF and two budget cards). ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Invalid sat cable number errors
On 17.04.2014 15:13, Ville Skyttä wrote: On Thu, Apr 17, 2014 at 3:22 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 17.04.2014 13:07, Ville Skyttä wrote: Hello, I see errors like the below on every VDR (2.0.6) startup and apparently exactly 30 minute intervals after that in syslog: ERROR: invalid sat cable number in '[apparent binary junk]' The binary junk varies, today it's been for example 'C0C0ۙ^?' and 'C00BEA48F^?' as shown by less. Any ideas what would be causing this or if I could do something to help debug this further? Please post (or send me via PM) the complete log from the very start of VDR up until the above error message. Sent in PM. Please also post the line DeviceBondings = ... from your setup.conf file. # grep DeviceBondings /etc/vdr/setup.conf DeviceBondings = 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 This is a DVB-C only system BTW (one FF and two budget cards). From your log: Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter0/frontend0 Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice Apr 17 16:03:21 vdr[16019]: [16019] new device number 1 Apr 17 16:03:21 vdr[16019]: [16019] frontend 0/0 provides DVB-C with QAM16,QAM32,QAM64,QAM128,QAM256 (ST STV0297 DVB-C) Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter1/frontend0 Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice Apr 17 16:03:21 vdr[16019]: [16019] new device number 2 Apr 17 16:03:21 vdr[16019]: [16019] frontend 1/0 provides DVB-C with QAM16,QAM32,QAM64,QAM128,QAM256 (ST STV0297 DVB-C) Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter2/frontend0 Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice Apr 17 16:03:21 vdr[16019]: [16019] new device number 3 Apr 17 16:03:21 vdr[16019]: [16019] frontend 2/0 provides DVB-C with QAM16,QAM32,QAM64,QAM128,QAM256 (VLSI VES1820 DVB-C) Apr 17 16:03:21 vdr[16019]: [16019] found 3 DVB devices Apr 17 16:03:21 vdr[16019]: [16019] initializing plugin: softhddevice (0.6.1rc1): A software and GPU emulated HD device Apr 17 16:03:21 vdr[16019]: [16019] new device number 9 What looks a little strange here is the gap between device number 3 and 9. Maybe this causes some misbehavior in handling device bonding? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Invalid sat cable number errors
On Thu, Apr 17, 2014 at 4:23 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 17.04.2014 15:13, Ville Skyttä wrote: On Thu, Apr 17, 2014 at 3:22 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: From your log: Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter0/frontend0 Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice Apr 17 16:03:21 vdr[16019]: [16019] new device number 1 Apr 17 16:03:21 vdr[16019]: [16019] frontend 0/0 provides DVB-C with QAM16,QAM32,QAM64,QAM128,QAM256 (ST STV0297 DVB-C) Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter1/frontend0 Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice Apr 17 16:03:21 vdr[16019]: [16019] new device number 2 Apr 17 16:03:21 vdr[16019]: [16019] frontend 1/0 provides DVB-C with QAM16,QAM32,QAM64,QAM128,QAM256 (ST STV0297 DVB-C) Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter2/frontend0 Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice Apr 17 16:03:21 vdr[16019]: [16019] new device number 3 Apr 17 16:03:21 vdr[16019]: [16019] frontend 2/0 provides DVB-C with QAM16,QAM32,QAM64,QAM128,QAM256 (VLSI VES1820 DVB-C) Apr 17 16:03:21 vdr[16019]: [16019] found 3 DVB devices Apr 17 16:03:21 vdr[16019]: [16019] initializing plugin: softhddevice (0.6.1rc1): A software and GPU emulated HD device Apr 17 16:03:21 vdr[16019]: [16019] new device number 9 What looks a little strange here is the gap between device number 3 and 9. Maybe this causes some misbehavior in handling device bonding? Dunno. I haven't told softhddevice to use any particular device number nor do I know if it's possible to do that. I've just configured it to set itself as the primary device. But are sat cable and device bonding valid concepts on DVB-C in the first place? The sat smells like DVB-S to me... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Invalid sat cable number errors
On 17.04.2014 16:09, Ville Skyttä wrote: On Thu, Apr 17, 2014 at 4:23 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 17.04.2014 15:13, Ville Skyttä wrote: On Thu, Apr 17, 2014 at 3:22 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: From your log: Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter0/frontend0 Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice Apr 17 16:03:21 vdr[16019]: [16019] new device number 1 Apr 17 16:03:21 vdr[16019]: [16019] frontend 0/0 provides DVB-C with QAM16,QAM32,QAM64,QAM128,QAM256 (ST STV0297 DVB-C) Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter1/frontend0 Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice Apr 17 16:03:21 vdr[16019]: [16019] new device number 2 Apr 17 16:03:21 vdr[16019]: [16019] frontend 1/0 provides DVB-C with QAM16,QAM32,QAM64,QAM128,QAM256 (ST STV0297 DVB-C) Apr 17 16:03:21 vdr[16019]: [16019] probing /dev/dvb/adapter2/frontend0 Apr 17 16:03:21 vdr[16019]: [16019] creating cDvbDevice Apr 17 16:03:21 vdr[16019]: [16019] new device number 3 Apr 17 16:03:21 vdr[16019]: [16019] frontend 2/0 provides DVB-C with QAM16,QAM32,QAM64,QAM128,QAM256 (VLSI VES1820 DVB-C) Apr 17 16:03:21 vdr[16019]: [16019] found 3 DVB devices Apr 17 16:03:21 vdr[16019]: [16019] initializing plugin: softhddevice (0.6.1rc1): A software and GPU emulated HD device Apr 17 16:03:21 vdr[16019]: [16019] new device number 9 What looks a little strange here is the gap between device number 3 and 9. Maybe this causes some misbehavior in handling device bonding? Dunno. I haven't told softhddevice to use any particular device number nor do I know if it's possible to do that. I've just configured it to set itself as the primary device. But are sat cable and device bonding valid concepts on DVB-C in the first place? The sat smells like DVB-S to me... These are purely sat related. I don't believe that the errors come from any tuning code, since actual device bonding is only done for DVB-S devices (see cDvbDevice::Bond()). Does this error occur if you make any changes to the setup? Like changing the OSD language or anything else that would cause the setup.conf file to be written. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Invalid sat cable number errors
Hi, I had exactly the same errors on my VDR (2.1.6): ERROR: invalid sat cable number in '°$Q‘ In my case the „binary junk“ is always °$Q, and the message appears also in a 30 min interval. After deactivating/removing the naludump patch, I can’t find the messages in the logs anymore. But this is just a guess and I don’t know if this is really related…. Am 17.04.2014 um 13:07 schrieb Ville Skyttä ville.sky...@iki.fi: Hello, I see errors like the below on every VDR (2.0.6) startup and apparently exactly 30 minute intervals after that in syslog: ERROR: invalid sat cable number in '[apparent binary junk]' The binary junk varies, today it's been for example 'C0C0ۙ^?' and 'C00BEA48F^?' as shown by less. Any ideas what would be causing this or if I could do something to help debug this further? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EIT related crash with 2.0.6
On 04/17/2014 01:01 PM, Ville Skyttä wrote: On Thu, Apr 17, 2014 at 10:56 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: Well, maybe epgsearch or epgfixer is messing something up? Does the problem happen if these plugins are not in use? It happens so rarely that it's most likely very hard to tell. I'll give it a shot without epgfixer but epgsearch is such an essential feature for this box that I don't think I'll be trying without it any time soon. I skimmed through both epgfixer and epgsearch sources quickly but didn't notice an obvious unlocked schedules access; it's entirely possible that I missed something though. I will go through the source of epgfixer thoroughly to see if any unlocked access to schedules can be found. -- Matti ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EIT related crash with 2.0.6
On 04/17/2014 08:06 PM, Matti Lehtimäki wrote: On 04/17/2014 01:01 PM, Ville Skyttä wrote: On Thu, Apr 17, 2014 at 10:56 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: Well, maybe epgsearch or epgfixer is messing something up? Does the problem happen if these plugins are not in use? It happens so rarely that it's most likely very hard to tell. I'll give it a shot without epgfixer but epgsearch is such an essential feature for this box that I don't think I'll be trying without it any time soon. I skimmed through both epgfixer and epgsearch sources quickly but didn't notice an obvious unlocked schedules access; it's entirely possible that I missed something though. I will go through the source of epgfixer thoroughly to see if any unlocked access to schedules can be found. I could not find any unlocked use of schedules in epgfixer, so it should not be the cause of problems. There is actually only one situation where schedules are modified and that happens only if epg data is cloned. -- Matti ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Invalid sat cable number errors
Am Donnerstag, 17. April 2014, 14:07:35 schrieb Ville Skyttä: I see errors like the below on every VDR (2.0.6) startup and apparently exactly 30 minute intervals after that in syslog: ERROR: invalid sat cable number in '[apparent binary junk]' to me this sounds like an invalid pointer. If I had such a bug I would try to run vdr under valgrind. -- Wolfgang ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Invalid sat cable number errors
On Thu, Apr 17, 2014 at 6:57 PM, Alexander Kniwel vdr-mailingl...@kniwel.net wrote: Hi, I had exactly the same errors on my VDR (2.1.6): ERROR: invalid sat cable number in '°$Q‘ In my case the „binary junk“ is always °$Q, and the message appears also in a 30 min interval. After deactivating/removing the naludump patch, I can’t find the messages in the logs anymore. But this is just a guess and I don’t know if this is really related…. Bingo, same thing here. Rebuilding VDR without the NALU dump patch gets rid of the error -- if the patch is in, it doesn't seem to make a difference if it's enabled in settings or not, the error is always there in syslog. Cc'ing patch author (@Udo: see below). Ville Am 17.04.2014 um 13:07 schrieb Ville Skyttä ville.sky...@iki.fi: Hello, I see errors like the below on every VDR (2.0.6) startup and apparently exactly 30 minute intervals after that in syslog: ERROR: invalid sat cable number in '[apparent binary junk]' The binary junk varies, today it's been for example 'C0C0ۙ^?' and 'C00BEA48F^?' as shown by less. Any ideas what would be causing this or if I could do something to help debug this further? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EIT related crash with 2.0.6
On Thu, Apr 17, 2014 at 9:58 PM, Matti Lehtimäki matti.lehtim...@gmail.com wrote: On 04/17/2014 08:06 PM, Matti Lehtimäki wrote: On 04/17/2014 01:01 PM, Ville Skyttä wrote: On Thu, Apr 17, 2014 at 10:56 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: Well, maybe epgsearch or epgfixer is messing something up? Does the problem happen if these plugins are not in use? It happens so rarely that it's most likely very hard to tell. I'll give it a shot without epgfixer but epgsearch is such an essential feature for this box that I don't think I'll be trying without it any time soon. I skimmed through both epgfixer and epgsearch sources quickly but didn't notice an obvious unlocked schedules access; it's entirely possible that I missed something though. I will go through the source of epgfixer thoroughly to see if any unlocked access to schedules can be found. I could not find any unlocked use of schedules in epgfixer, so it should not be the cause of problems. There is actually only one situation where schedules are modified and that happens only if epg data is cloned. Thanks, I found out that running without epgfixer for a long time wasn't really an option. In the meantime, the third plugin I have that deals with EPG is live which I haven't really used. Will try without it but I'm already certain that if live is to blame, it's not something related to its interactive use but some background task if it has any. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Invalid sat cable number errors
On Thu, Apr 17, 2014 at 1:28 PM, Ville Skyttä ville.sky...@iki.fi wrote: naludump How much disk space do you actually save using that? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
