Newifi-D2 getting kern.warn messages on OpenWrt 19.07.7 r11306-c4a6851c72

I've updated my Newifi-D2 (MediaTek MT7621 ver:1 eco:3) this morning with the latest 19.07.7 r11306-c4a6851c72, coming from 19.07.6 I'm now seeing these in the logs, where I didn't have them before updating. It's come up twice since this morning. Doesn't seem to have any noticable effect on connected devices, should I be worried my router will crash while I'm in the middle of an online meeting?

Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017267] ------------[ cut here ]------------
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017304] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:320 0x8038d700
Thu Feb 18 19:28:46 2021 kern.info kernel: [ 7375.017310] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 0 timed out
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017315] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_ipv6 mt76x2e mt76x2_common mt76x02_lib mt7603e mt76 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt compat sch_cake nf_conntrack sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017553]  cls_tcindex cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred ledtrig_usbport nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ifb leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd gpio_button_hotplug usbcore nls_base usb_common
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017653] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.221 #0
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017660] Stack : 00000000 00000000 00000000 8fd8ff40 00000000 00000000 00000000 00000000
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017689]         00000000 00000000 00000000 00000000 00000000 00000001 8fc09d60 ac07f5c4
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017718]         8fc09df8 00000000 00000000 00005a50 00000038 8049e2b8 00000001 00000000
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017746]         00000000 80550000 00000119 806e0000 8fc09d40 00000000 00000000 8050d500
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017775]         8038d700 00000140 00000000 8fd8ff40 00000001 80550000 00000000 806b0000
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017804]         ...
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017812] Call Trace:
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017869] [<8049e2b8>] 0x8049e2b8
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017880] [<8038d700>] 0x8038d700
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017895] [<8000c1a0>] 0x8000c1a0
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017901] [<8000c1a8>] 0x8000c1a8
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017906] [<804870f4>] 0x804870f4
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017912] [<80071e00>] 0x80071e00
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017926] [<8002e798>] 0x8002e798
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017932] [<8038d700>] 0x8038d700
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017947] [<8002e820>] 0x8002e820
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017966] [<8038d700>] 0x8038d700
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017971] [<80099da0>] 0x80099da0
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017982] [<8038d554>] 0x8038d554
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017988] [<80088948>] 0x80088948
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.017993] [<8035d6bc>] 0x8035d6bc
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.018004] [<80088c04>] 0x80088c04
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.018010] [<800794a8>] 0x800794a8
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.018022] [<804a50b8>] 0x804a50b8
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.018031] [<80033164>] 0x80033164
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.018037] [<8025b710>] 0x8025b710
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.018044] [<80007488>] 0x80007488
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.018048]
Thu Feb 18 19:28:46 2021 kern.warn kernel: [ 7375.018054] ---[ end trace 3d9734e1af51a4f7 ]---
Thu Feb 18 19:28:46 2021 kern.err kernel: [ 7375.018070] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out
Thu Feb 18 19:28:46 2021 kern.info kernel: [ 7375.018080] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000065
Thu Feb 18 19:28:46 2021 kern.info kernel: [ 7375.018094] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=0f1b0000, max=0, ctx=2532, dtx=2532, fdx=2531, next=2532
Thu Feb 18 19:28:46 2021 kern.info kernel: [ 7375.018106] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=0e540000, max=0, calc=3417, drx=3418
Thu Feb 18 19:28:46 2021 kern.info kernel: [ 7375.021406] mtk_soc_eth 1e100000.ethernet: 0x100 = 0x6060000c, 0x10c = 0x80818
Thu Feb 18 19:28:46 2021 kern.info kernel: [ 7375.026764] mtk_soc_eth 1e100000.ethernet: PPE started
Thu Feb 18 20:12:32 2021 daemon.err uhttpd[1733]: luci: accepted login on /admin/status/syslog for root from 192.168.1.191
Thu Feb 18 20:15:08 2021 kern.info kernel: [10156.279290] mtk_soc_eth 1e100000.ethernet eth0: port 0 link up

I think that's a known problem with the ethernet driver for the MT7621 platform in 19.07 / with kernel 4.14, the pending release (21.02) will have a newer upstream driver that doesn't suffer from that issue.

If you want, you can already give the buildbot images a try, do keep in mind though you need to wipe configuration since 21.02 switches to DSA (most settings might actually carry over, but you need to wipe /etc/config/network). So back up your configs, but do wipe, otherwise you will render your device inaccessible.

If you are concerned with stability, I've been running master builds on my MT7621 devices for months now. Already have one MT7621 testing device on a personal 21.02 build. Will be switching my 'production' devices shortly.

2 Likes

Thanks for the advice. I want to try the snapshot but not sure if I know how to correctly install it... Is installing the 21.02 snapshot as straight forward as as upgrading to a stable release via luci?

Meanwhile I've gone back to 19.07.6

It is. It's easier to do it through SSH though. Copy it over to /tmp/ on your router, SSH in, verify the checksum, and issue the following command:

# sysupgrade -n -F /tmp/$name_of_your_sysupgrade_image

Thanks, wish me luck!

1 Like

Keep in mind that the snapshot does not have LuCI installed.

You can do so by ssh'ing into the router and run this command:

opkg update && opkg install luci
1 Like

If all is well 21.02 snapshots do. They're pre-release images after all, just like 19.07 had snapshots at one point.

1 Like

Surprisingly it did come preinstalled with LuCI. I've succesfully installed the 21.02 snapshot, so far so good.

it still does have this bug with my Oneplus 5T on 2.4G, system log is flooded with the below and slows all other devices connection down. It was present on 19.07.6 and .7 too

Fri Feb 19 00:18:10 2021 daemon.notice hostapd: wlan0: STA-OPMODE-SMPS-MODE-CHANGED 8a:d4:7f:2b:14:14 off
Fri Feb 19 00:19:20 2021 daemon.notice hostapd: wlan0: STA-OPMODE-SMPS-MODE-CHANGED 8a:d4:7f:2b:14:14 static

Other than that, seems stable in the 12 hours since the install.

1 Like

Doh, confused snapshots with master branch builds

This might be a solution, the info why this message crops up is also in that thread:

1 Like

Saw that, but the Oneplus 5T doesn't have that option. Not a big deal, 5GHz range is suitable for this small house.

Hi,
You advised: "....do keep in mind though you need to wipe configuration since 21.02 switches to DSA "
I downloaded the latest snapshot openwrt-ramips-mt7621-d-team_newifi-d2-squashfs-sysupgrade.bin Mon Feb 22 05:57:09 2021and DSA is not enabled. The Ethernet driver for the 19.07.xx MT7621 anomaly is not present.

How is that? If you flashed without keeping configs, do this:

grep -B 2 "lan[1-4]" /etc/config/network

Borromini,
Thank you for the prompt response.
WIFI channels > 48 are not recognized.

grep -B 2 "lan[1-4]" /etc/config/network
config interface 'lan'
        option type 'bridge'
        option ifname 'lan1 lan2 lan3 lan4'

That's your DSA right there.

DFS isn't DSA. You should raise your question in a separate topic instead of hijacking this one.