On 27.11.2017 09:04, Teemu Suikki wrote:
I made this change few hours ago, but I'm still waiting for the
problem to appear.. Obviously it now is working 100%. :)
Does "working 100%" mean that youre not getting any of these error
messages any more? Not even once?
Klaus
2017-11-27 0:08 GMT+02:00 Klaus Schmidinger <Klaus.Schmidinger@xxxxxxx>:
On 26.11.2017 19:09, Teemu Suikki wrote:
I know I'm replying to a year old thread, but I'm having the exact same
problem.
I upgraded my system from kernel 3.16.0 to 4.4.0, and also TBS dvb
drivers to latest version.. Now I have this problem, that randomly VDR
starts flooding this "ERROR: TS packet not accepted in Transfer Mode"
log. It will not jam right away, but after maybe 30-60min it is
jammed.
Some VDR functions like timers seem to still work, but the GUI is stuck.
This is VDR 2.2.0 from yavdr repos.
Any ideas?
Even though this might be a driver bug, perhaps vdr of softhddevice
could simply stop displaying the channel after the first error?
I can't contribute anything regarding the driver or softhddevice,
but I guess limiting the log message to, say, one message per minute
could save the program from getting stuck.
That's assuming your log is actually flooded with thousands of
entries like that.
To qickly verify this could you please precede the line
esyslog("ERROR: TS packet not accepted in Transfer Mode");
in transfer.c with
static int Counter = 0;
if ((Counter++ % 10000) == 0)
Klaus
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
