Mtk_soc_eth watchdog timeout after r11573

pre-pre-pre reliase 21.02
https://downloads.openwrt.org/releases/21.02-SNAPSHOT/targets/

1 Like

Thanks a lot. Installed and running fine the last couple of days.

Should I avoid Software and/or Hardware Flow Offloading on the snapshots?

Try tomorrow's snapshot build! You have to build the test kernel, as it's for 5.10

It will include commit 0d5bf53197481d291f9a541eefa03b11a34033f9

And please test sw/hw flow-offload!

1 Like

Oh now that is timely!! Will do thanks.

it`s patch to 5.10 kernel - base to future (23.13 or later :slight_smile: release.
5.4 kernel and offloading i tested in 410 post = work at least for IPoE

1 Like

Yup! You are right! One should select testing kernel to use it.

21.02 pre (kernel 5.4) work enough good for my case

I am also using OpenWRT on an EdgeRouter X (Cable Modem WAN) and the device was going down on a daily basis as you mentioned. Based on the inputs from this forum I upgraded to the snapshot builds in January. While there was not a single freeze since then, the internet connection stops randomly several times a day. I already had it checked by my ISP and the modem and even the WAN port of the ERX are accessible during these outages. So it seems to be a routing problem.
So I just reinstalled 19.07.7 following this guide:
Ubiquiti EdgeRouter X, Loading OpenWrt and performance numbers
This time I also moved the WAN connection to eth4 (according to the instructions this is a tweak, but it is not explained why). The system has been up for a day now without an issue.

I have been running snapshot r16165-0183ee2eb9 for a while. Moved to this after running into issues with 19.07.7. No issues so far, I didn't enable any offloading. BTW, moved from edgeos2.x to openwrt a week back.

I am using D-Link D-860L B1 as AP, running snapshots that was updated once mt76 got an update. It's very stable now, with much less interrupt errors.

While the EdgeRouter is still up and running I am again experiencing interruptions in the connection several times a day. I will try using the snapshot build to see if it makes a difference.

As I was still experiencing connection drops so I reverted to EdgeOS 1.10.11 which is running now without an issue.

I also saw the same issue with the Snapshot build until I disabled Software and Hardware Flow Offloading. Since doing that, it has been rock solid and up now 12 days and counting.

1 Like

Thank you for this feedback. I am aware, that offloading cannot be used together with sqm. But in my case offloading was also disabled. With earlier 19.07 builds I had the problem complete locks of the router which occurred randomly. With the newer builds these locks are gone and the ERX is stable for a long time. Nevertheless, now the connection drops about once or twice a day (also randomy with messages like "mt7530 mdio-bus:00 lan4: Link is Down" ) but just for a minute or so and everything is back to normal afterwards. This is not a problem for browsing the web, but it is a problem for streaming or video conferencing. That's why I reverted back to the stock firmware.

Yes I am noticing the same now for FaceTime. Disconnects video every 30-40 seconds for a few seconds.

I have been using 21.02 snapshot without an issue for a while. I use zoom and kids use MS teams, no issues so far.

Are you also using PPoe with VLan tagging?

No ppoe, no vlan tagging.

So far so good with the 20.02 snapshots for me personally, so very happy with that. Unfortunately, I do still run into another issue, where the port randomly disconnects and reconnects. Anyone experiencing the same issue? This is just getting spammed over and over again in my dmesg log:

[2612337.641359] mt7530 mdio-bus:1f lan1: Link is Down
[2612337.646999] br-lan: port 1(lan1) entered disabled state
[2612378.601396] mt7530 mdio-bus:1f lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[2612378.609641] br-lan: port 1(lan1) entered blocking state
[2612378.615187] br-lan: port 1(lan1) entered forwarding state
[2637278.061031] mt7530 mdio-bus:1f lan1: Link is Down
[2637278.066413] br-lan: port 1(lan1) entered disabled state
[2671089.335938] mt7530 mdio-bus:1f lan1: Link is Up - 100Mbps/Full - flow control off
[2671089.343678] br-lan: port 1(lan1) entered blocking state
[2671089.349144] br-lan: port 1(lan1) entered forwarding state
[2671164.087303] mt7530 mdio-bus:1f lan1: Link is Down
[2671164.092606] br-lan: port 1(lan1) entered disabled state
[2671167.159559] mt7530 mdio-bus:1f lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[2671167.167322] br-lan: port 1(lan1) entered blocking state
[2671167.172800] br-lan: port 1(lan1) entered forwarding state
[2671355.670475] mt7530 mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control off
[2671355.678021] br-lan: port 2(lan2) entered blocking state
[2671355.683440] br-lan: port 2(lan2) entered forwarding state
[2671398.678004] mt7530 mdio-bus:1f lan2: Link is Down
[2671398.683057] br-lan: port 2(lan2) entered disabled state
[2671401.750238] mt7530 mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
[2671401.757974] br-lan: port 2(lan2) entered blocking state
[2671401.763405] br-lan: port 2(lan2) entered forwarding state
[2671690.516396] mt7530 mdio-bus:1f lan2: Link is Down
[2671690.521708] br-lan: port 2(lan2) entered disabled state
[2671720.212390] mt7530 mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
[2671720.220236] br-lan: port 2(lan2) entered blocking state
[2671720.225687] br-lan: port 2(lan2) entered forwarding state

If more people are experiencing this, it might warrant a new topic maybe?

I think it may be a bad cable.

1 Like