Tvheadend

same for me when I tried to test latest version for DiseqC fixes, also I get

2015-03-22 17:23:55.592 linuxdvb: STV090x Multistandard : DVB-S #0 - read() EOVERFLOW
2015-03-22 17:23:55.716 linuxdvb: STV090x Multistandard : DVB-S #3 - read() EOVERFLOW
2015-03-22 17:23:56.973 linuxdvb: STV090x Multistandard : DVB-S #3 - read() EOVERFLOW
2015-03-22 17:23:57.026 linuxdvb: STV090x Multistandard : DVB-S #0 - read() EOVERFLOW
2015-03-22 17:23:57.417 linuxdvb: STV090x Multistandard : DVB-S #2 - read() EOVERFLOW

and it doesn't take longe till the whole system locks up.

What values are printed using this patch ?

iff --git a/src/input/mpegts/linuxdvb/linuxdvb_frontend.c b/src/input/mpegts/linuxdvb/linuxdvb_frontend.c
index b58d617..c433298 100644
--- a/src/input/mpegts/linuxdvb/linuxdvb_frontend.c
+++ b/src/input/mpegts/linuxdvb/linuxdvb_frontend.c
@@ -949,7 +949,9 @@ linuxdvb_frontend_input_thread ( void *aux )
     }

     /* Process */
+    printf("sb_ptr before: %i\n", sb.sb_ptr);
     mpegts_input_recv_packets((mpegts_input_t*)lfe, mmi, &sb, NULL, NULL);
+    printf("sb_ptr after: %i\n", sb.sb_ptr);
   }

   sbuf_free(&sb);

188 byte packages.....

2015-03-22 18:19:25.916 [ INFO] htsp: Got connection from 192.168.0.245
sb_ptr before: 188
sb_ptr after: 188
sb_ptr before: 376
sb_ptr after: 376
sb_ptr before: 564
sb_ptr after: 564
sb_ptr before: 940
sb_ptr after: 940
sb_ptr before: 1316
sb_ptr after: 1316
sb_ptr before: 1692
sb_ptr after: 1692
sb_ptr before: 2068
sb_ptr after: 2068
sb_ptr before: 2444
sb_ptr after: 2444
sb_ptr before: 2632
sb_ptr after: 2632
2015-03-22 18:19:26.061 [ INFO] AVAHI: Service 'Tvheadend' successfully established.
sb_ptr before: 2820
sb_ptr after: 2820
sb_ptr before: 3008
sb_ptr after: 3008
2015-03-22 18:19:26.075 [ INFO] htsp: Got connection from 192.168.0.6
2015-03-22 18:19:26.079 [ INFO] htsp: 192.168.0.6: Welcomed client software: Kodi Media Center (HTSPv12)
2015-03-22 18:19:26.079 [ INFO] htsp: 192.168.0.6 [ Kodi Media Center ]: Disconnected
sb_ptr before: 3196
sb_ptr after: 3196
sb_ptr before: 3384
sb_ptr after: 3384
sb_ptr before: 3572
sb_ptr after: 3572
sb_ptr before: 3760
sb_ptr after: 3760
sb_ptr before: 3948
sb_ptr after: 3948
sb_ptr before: 4136
sb_ptr after: 4136
sb_ptr before: 4324
sb_ptr after: 4324
sb_ptr before: 4512
sb_ptr after: 4512
sb_ptr before: 4700
sb_ptr after: 4700
sb_ptr before: 4888
sb_ptr after: 4888
sb_ptr before: 5076
sb_ptr after: 5076
sb_ptr before: 5264

When the streaming is active.. The buffer is processed when the size is over 18800 bytes or when a second is changed (time).

I applied the patch but I don't know how to get the "printf" results. I use /etc/init.d/tvheadend to start tvheadend and the only information is printed to syslog. :-(

br
Alfred

ok, if you need more than the following let me know, this is where it wrapps from 18800 to 0...,

sb_ptr before: 17484
sb_ptr after: 17484
sb_ptr before: 17860
sb_ptr after: 17860
sb_ptr before: 18236
sb_ptr after: 18236
sb_ptr before: 18424
sb_ptr after: 18424
sb_ptr before: 18800
sb_ptr after: 0
sb_ptr before: 376
sb_ptr after: 376
sb_ptr before: 564
sb_ptr after: 564
sb_ptr before: 940

Alfred Zastrow wrote:

I applied the patch but I don't know how to get the "printf" results. I use /etc/init.d/tvheadend to start tvheadend and the only information is printed to syslog. :-(

br
Alfred

start it from the cmd line, like ./build.linux/tvheadend and you will get output in the console

Same on my system with 3.9.2612~gc61be4e, seems to be no problem at the moment for watching/recording channels.

well for me it's not looking that good, beside the read() EOVERFLOW my system crashes and it tries to retune forever until it vanishs

correcting myself, it indeed is working and just displays discontinuities, a cold boot fixed my EOVERFLOW error

Jaroslav Kysela wrote:

What values are printed using this patch ?

[...]

This patch only changes something on DVB, right? It happens here also with pipe://-channels...

Fixed in v3.9-2623-gc308e17 . Thanks for the report, I overlooked it (and EOVERFLOW threw my head to totally different mode :-) but the comment#12 recovered it).

Thanks for fixing so fast. Version 3.9.2624~gdb5cf2a doesn't show Continuity errors anymore on my system.