Trying to continue discussion about blog mcast error from
@Torson without hijacking his thread any more.
https://www.snbforums.com/threads/w...throughput-and-flood-of-syslog-entries.70937/
both
@doczenith1 and
@chongnt reported seeing these errors on ac86u and when I went through my scribe filters I found the same at some specific times, today between 15:57 - 16:17 there are about 100 of these:
Code:
May 12 16:15:26 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
May 12 16:15:26 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
May 12 16:15:44 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
May 12 16:15:44 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
May 12 16:15:57 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
May 12 16:15:57 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
May 12 16:16:20 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
May 12 16:16:20 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
May 12 16:16:41 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
May 12 16:16:41 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
May 12 16:17:01 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
May 12 16:17:01 RT-AC86U-D7D8 kernel: [0;33;41m[ERROR mcast] bcm_mcast_blog_process,789: blog allocation failure[0m
They seem to come in pair of 2 and usually ~20 sec in between. There have been wast internet usage after this that dont produce any error so it seems to be linked to some special packages from some app I presume (my doughter was the only one home at the time so possibly youtube).
I have not seen any drop in throughput, still gets 100/100, same as my subscription. Nor have I seen any issues for normal usage).
Is it even caused by wireguard or something else?
I have started thinking about possible conflicts between the Xmark set by wgm to bypass hw-acceleration and other marks, like ipset marks (fwmark and Xmark are the same right? Just Xmark XOR the value with the mask). Don't we mess up this mark when marking packages for I.e ipset routing?
Pinging
@Martineau as he usually has great knowledge about these stuff.