Hi. I bought the ER-X 1 month ago and flashed it with own compiled LEDE 17.01.7 with Qualcomm Fast Path patch for Kernel 4.4 (Qualcomm Fast Path For LEDE). Since then almost every day I have these errors in the System Log:
What causes the connection to the router is lost a few seconds until it recovers. Other times it stays "fried", the router cannot be accessed, and there is no communication between the ethernet ports until I restart it. Also sometimes after restarting it within a few hours, I find this in the Kernel Log:
It seems like a problem with the switch. I don't know if the patch has anything to do with it, but since i have searched and although there are many with the same problem i discard this. Although there is no definitive solution, some say that disabling flow control is solved, but I cannot disable it with ethtool because it is not implemented in the driver. I tried to disable it in the equipment and switch connected to it, but i think there is still a port (eth0) with the flow control enabled because I cannot deactivate it in the FTTH ONT.
Does anyone know how I could fix it once and for all? Any patch for the Ethernet driver?
Not yet, later I will install 17.01.7 without the patch and try a few days. If the error persists I will try the 19.07 snapshot. But I have no faith that it works, since there are different messages with the same problem even with 18.06.X:
Well, for now it has been running without errors with official lede 17.01.7 for two days (without patches), and without the kmod-sched-core module that I have read that generates problems in the MT7621 soc and I had it in my compilation. I will wait 3 more days and compile again with the Qualcomm patch but without kmod-sched-core.
Any specific reason you went for 17.01.7 instead of the 18.06.4 / 19.07 or just building from the master? Available packages must be pretty outdated, as well as fewer kernel options.
On my ERX I've switched to building from the master branch pretty quickly since first using the stable 18.06.x, then snapshots. In terms of stability, performance, etc - no negatives to report. There was a snapshot in July I think that caused kernel panic when hardware flow offload was enabled, but it had since been fixed. I've recently switched default congestion control to BBR - it's been working quite well.
I prefer a stable version to update every bit. I also prefer 17.01.x to 18.06.x or the latter really for aesthetic reasons of LuCI. It may also consume more resources (ram). I don't like how the wan interface is shown on the overview page, nor the action buttons (apply, cancel, add, delete...) that are not filled, or the spacing between each line or elements (for example the routes and arp, connections, firewall rules, etc.) If I get 17.01.7 to work stable 24/7 all time I will continue with it for a long time.
17 is EOL and will receive no further updates (including no security updates, AFAIK). 18 is effectively in maintenance mode (nothing new here, nor many, if any bug fixes). 19 is already a thousand commits behind master and it hasn’t even been released yet.
LuCI can easily be installed on a snapshot, or added with the image builder.
After 4 days and 8 hours without any error in system log "transmit timed out", the router has become frozen again having to disconnect and connect it to the power, without being able to read the log. I will have to compile 19.07 or master branch.