Great, one user already commented long ago that having each port in a separate VLAN had no transmit timed out or reboots. But I thought it was because he got a "good" SoC. I will prove it. At the moment I am using the mt7530_fix patch with fcoff and although i have transmit timed outs every 2 days, it seems that it does not restart or hang. Are you using any patch or stable version as it comes? Is there any degradation in performance between local transfers on the ports of the software bridge or use more cpu?
I still don't want to switch to kernel 5.4 for "complexity" to configure VLANs in the DSA driver.
Unfortunately, it seems like I jinxed it. The connected was down and the router unreachable for ~20 minutes. The issue cleared itself up eventually, but at the time of the issue the dreaded error was found in the kernel log.
@dchard and others that are testing a build with the 5.4 kernel, is this problem fixed on the 5.4 kernel? How is overall stability on these bleeding edge builds? Is it worth using over a 19.07.2 build on production hardware? Or should I bite the bullet and abandon this platform?
My mir3g has an uptime of 3 days with r13042 + my modifications and I haven't run into the problem.
However, I don't have a very fancy setup. Just an USB 4GLTE dongle and atm 3-4 WiFi clients connected to 5 GHz.
When I had uplink 80mbit @ 100mbit port, I got no problem.
Now, 100@100 whith FC on at provider switch, I get "transmit queue 0 timed out" on all OWRT device, including MT7621 (Mi3G)
For example, after 3-10 minuts at torrent whith 100 mbit download
tl-wr741nd ver 2.4 target ar71xx/ath79
If what causes these problems is flow control, why in 4.14 disabling it the problems continue? I still think that before switching to kernel 5.4 with DSA driver this should have been fixed.
I see high amounts of interrupt errors when checking /proc/interrupts. Most likely from the wifi chips. Is this of any relevance? On my r7800 I don't have any errors ...
I tried several times compile and flash kernel 5.4 firmware for rampis MT7621, network and switcher never work. Ping to router always timeout. Now still keep stay on 19.07-SNAPSHOT branch with kernel 4.14.176.
Thanks, it does help me a lot, as I need to stay on 4.14 / 19.07.x base, and these patches seem to stabilize the router.
I have a specific issues that just surfaced when switching from a Netgear CM600 to a CM1000 cable modem. The router just constantly reboots on the CM1000, so I suspect it is using Pause frames and causes the router to crash and reboot. So the FC off patch would likely help, right?
Anyone know how to turn of Flow control on port 5 on an existing deployment?
I can't deploy a new build until several weeks from now, but would love to be able to run a cli command or edit a setting to turn off FC so that unit can run with the CM1000.
I have 16+ days of uptime on 5.4.35, and have no kernel errors whatsoever. (Dlink 860L). And one leg of the router still has flow control enabled (all gigabit).
Or you can give the latest maser a try. I am running on it for quite some time, have no errors whatsoever.
Activating the second RGMII link can cause issues, if I remember correctly this is explained this in the v5.4 PR by one of the developers. Take a look before you proceed.