( or i'll put something in luci for next time to easily dump the debug stuff to PM )
now that you mention the testing-build... two important notes worth mentioning, i'm testing out;
update signing
no irqbalance
so if anyone notices general responsiveness improvements or gets a message when they upgrade like 'image is incompatible use -F'...
let me know.... honestly I think irqbalance has some small benefits on the network side... but removing it seems to improve general OS scheduler function...
kind of nor here nor there... but probably useful to see how it goes for everyone not enabled...
not build related... needs a new thread ( well, based on what you've shown there is no clear question here... only how to interpret graphs )...
everything 'sqm' is always relative to load, settings and baseline 'line' capabilities...
the only really clear piece of (usable) info someone can make a guestimate of based on what you posted are the 'latency' characteristics under no-load... which are typically indicative of physical line properties and not sqm.
I have one more question.
I am unable to access my modem now.
before the update i think it was working fine.
I did setup modem interface as mentioned here
Thu Jan 14 13:24:12 2021 daemon.warn avahi-daemon[9809]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Thu Jan 14 13:24:12 2021 daemon.err avahi-daemon[9809]: dbus_bus_get_private(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Thu Jan 14 13:24:12 2021 daemon.warn avahi-daemon[9809]: WARNING: Failed to contact D-Bus daemon.
the dbus stuff would be related to samba... and the fact dbus is now built-in (for...something else) and default disabled... so you have to enable dbus ... and/or add it to ENABLEDSERVICES
I dont think I changed any settings
other than creating a WIFI
new errors is it normal?
Thu Jan 14 13:52:48 2021 daemon.err collectd[10521]: Sleeping only 2s because the next interval is 2.451 seconds in the past!
Thu Jan 14 13:53:09 2021 daemon.err dnsmasq[6904]: failed to send packet: Operation not permitted
if you didn't change settings... then it might have been something @ new package migration scripts... ( not specifically build related )... edit: checked these and nothing special there unless it came down with igmproxy package... checked that too and don't see anything interesting... i'm guessing it's probably some sort of service start race condition or something ( restarting igmpproxy or firewall probably would have fixed it )
if you do a backup of all the files in /etc/config then compare those with all the files in /etc/config from your working backup... you can find what the issue is...