Error Interpretation

Installing and Using OpenWrt
1

So when I have online classes, the router suddenly goes into a reboot sequence, disrupting it. I found an error, but I don't know what it means.

Here's the system log for reference.

Sun Oct  4 19:02:09 2020 user.notice SQM: piece_of_cake.qos was started on eth0.2 successfully
Sun Oct  4 19:02:10 2020 user.notice firewall: Reloading firewall due to ifup of wan (eth0.2)
Sun Oct  4 19:02:10 2020 daemon.info dnsmasq[1896]: read /etc/hosts - 4 addresses
Sun Oct  4 19:02:10 2020 daemon.info dnsmasq[1896]: read /tmp/hosts/odhcpd - 2 addresses
Sun Oct  4 19:02:10 2020 daemon.info dnsmasq[1896]: read /tmp/hosts/dhcp.cfg01411c - 3 addresses
Sun Oct  4 19:02:10 2020 daemon.info dnsmasq-dhcp[1896]: read /etc/ethers - 0 addresses
Sun Oct  4 19:15:56 2020 daemon.info hostapd: wlan0: STA b2:be:76:5c:47:0e IEEE 802.11: authenticated
Sun Oct  4 19:15:56 2020 daemon.info hostapd: wlan0: STA b2:be:76:5c:47:0e IEEE 802.11: associated (aid 1)
Sun Oct  4 19:15:56 2020 daemon.info dnsmasq-dhcp[1896]: DHCPREQUEST(br-lan) 192.168.9.100 b2:be:76:e4:6c:7c
Sun Oct  4 19:15:56 2020 daemon.info dnsmasq-dhcp[1896]: DHCPNAK(br-lan) 192.168.9.100 b2:be:76:e4:6c:7c address not available
Sun Oct  4 19:15:57 2020 daemon.notice hostapd: wlan0: AP-STA-CONNECTED b2:be:76:5c:47:0e
Sun Oct  4 19:15:57 2020 daemon.info hostapd: wlan0: STA b2:be:76:5c:47:0e WPA: pairwise key handshake completed (RSN)
Sun Oct  4 19:15:58 2020 daemon.info hostapd: wlan0: STA b2:be:76:41:ab:3a IEEE 802.11: authenticated
Sun Oct  4 19:15:58 2020 daemon.info hostapd: wlan0: STA b2:be:76:16:2b:31 IEEE 802.11: authenticated
Sun Oct  4 19:15:58 2020 daemon.info hostapd: wlan0: STA b2:be:76:41:ab:3a IEEE 802.11: associated (aid 2)
Sun Oct  4 19:15:58 2020 daemon.info hostapd: wlan0: STA b2:be:76:16:2b:31 IEEE 802.11: associated (aid 3)
Sun Oct  4 19:15:59 2020 daemon.notice hostapd: wlan0: AP-STA-CONNECTED b2:be:76:41:ab:3a
Sun Oct  4 19:15:59 2020 daemon.info hostapd: wlan0: STA b2:be:76:41:ab:3a WPA: pairwise key handshake completed (RSN)
Sun Oct  4 19:15:59 2020 daemon.notice hostapd: wlan0: AP-STA-CONNECTED b2:be:76:16:2b:31
Sun Oct  4 19:15:59 2020 daemon.info hostapd: wlan0: STA b2:be:76:16:2b:31 WPA: pairwise key handshake completed (RSN)
Sun Oct  4 19:16:00 2020 daemon.info dnsmasq-dhcp[1896]: DHCPDISCOVER(br-lan) b2:be:76:e4:6c:7c
Sun Oct  4 19:16:00 2020 daemon.info dnsmasq-dhcp[1896]: DHCPOFFER(br-lan) 192.168.0.114 b2:be:76:e4:6c:7c
Sun Oct  4 19:16:00 2020 daemon.info dnsmasq-dhcp[1896]: DHCPINFORM(br-lan) 192.168.0.198 08:62:66:87:3c:87
Sun Oct  4 19:16:00 2020 daemon.info dnsmasq-dhcp[1896]: DHCPACK(br-lan) 192.168.0.198 08:62:66:87:3c:87 CHIDOWS
Sun Oct  4 19:16:00 2020 daemon.info dnsmasq-dhcp[1896]: DHCPREQUEST(br-lan) 192.168.0.114 b2:be:76:e4:6c:7c
Sun Oct  4 19:16:00 2020 daemon.info dnsmasq-dhcp[1896]: DHCPACK(br-lan) 192.168.0.114 b2:be:76:e4:6c:7c Blastorix
Sun Oct  4 19:16:14 2020 daemon.info dnsmasq-dhcp[1896]: DHCPDISCOVER(br-lan) 192.168.9.28 b0:be:76:5c:47:0d
Sun Oct  4 19:16:14 2020 daemon.info dnsmasq-dhcp[1896]: DHCPOFFER(br-lan) 192.168.9.28 b0:be:76:5c:47:0d
Sun Oct  4 19:16:21 2020 daemon.err uhttpd[1406]: luci: accepted login on / for root from 192.168.0.114
Sun Oct  4 19:16:24 2020 daemon.err miniupnpd[2042]: upnp_event_recv: recv(): Connection reset by peer
Sun Oct  4 19:16:24 2020 daemon.err miniupnpd[2042]: upnpevents_processfds: 0x428ee0, remove subscriber uuid:3db9bf35-885d-4044-a51a-39e3f9cd7e1f after an ERROR cb: http://192.168.0.114:2869/upnp/eventing/drjplcpwkp
Sun Oct  4 19:16:24 2020 daemon.err miniupnpd[2042]: upnp_event_recv: recv(): Connection reset by peer
Sun Oct  4 19:16:24 2020 daemon.err miniupnpd[2042]: upnpevents_processfds: 0x428ee0, remove subscriber uuid:feff367f-a245-409a-9f0e-955d64e4d4cd after an ERROR cb: http://192.168.0.114:2869/upnp/eventing/lttlucmhzy

How do I solve this? It's a recurring issue, much to my annoyance.

2

Here's another error log for reference:

Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.148649] ------------[ cut here ]------------
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.153365] WARNING: CPU: 0 PID: 135 at net/sched/sch_generic.c:320 0x802c5530
Sun Oct  4 19:34:24 2020 kern.info kernel: [   97.160714] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 0 timed out
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.167766] Modules linked in: pppoe ppp_async mt76x0e mt76x0_common pppox ppp_generic nf_conntrack_ipv6 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
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.239661]  cls_tcindex cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ifb leds_gpio gpio_button_hotplug
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.260891] CPU: 0 PID: 135 Comm: kworker/0:1 Not tainted 4.14.195 #0
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.267425] Workqueue: mtdblock6 0x80248654
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.271685] Stack : 80401aa8 80428c10 802c5530 00000140 00000000 00000000 00000000 00000000
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.280188]         00000000 00000000 00000000 00000000 00000000 00000001 83807de0 9badf702
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.288690]         83807e78 00000000 00000000 00004ab0 00000038 803ce8b8 00000008 00000000
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.297193]         00000000 80460000 000414a1 00000000 83807dc0 00000000 00000000 80428c10
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.305692]         802c5530 00000140 8046ff34 8046fef4 00000002 8021cfc0 00000000 805b0000
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.314194]         ...
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.316674] Call Trace:
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.316685] [<802c5530>] 0x802c5530
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.322755] [<803ce8b8>] 0x803ce8b8
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.326297] [<802c5530>] 0x802c5530
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.329859] [<8021cfc0>] 0x8021cfc0
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.333412] [<8000aa50>] 0x8000aa50
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.336949] [<8000aa58>] 0x8000aa58
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.340518] [<80026480>] 0x80026480
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.344061] [<802c5530>] 0x802c5530
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.347608] [<80026508>] 0x80026508
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.351176] [<8026dcf0>] 0x8026dcf0
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.354732] [<802c5530>] 0x802c5530
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.358274] [<802c53cc>] 0x802c53cc
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.361831] [<8005ffcc>] 0x8005ffcc
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.365366] [<8000e0a4>] 0x8000e0a4
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.368938] [<800601a0>] 0x800601a0
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.372480] [<8029f018>] 0x8029f018
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.376036] [<803d4368>] 0x803d4368
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.379592] [<8005a554>] 0x8005a554
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.383136] [<80055ab0>] 0x80055ab0
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.386687] [<80005e90>] 0x80005e90
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.390249]
Sun Oct  4 19:34:24 2020 kern.warn kernel: [   97.391759] ---[ end trace 84e477b663a68a65 ]---
Sun Oct  4 19:34:24 2020 kern.err kernel: [   97.396452] mtk_soc_eth 10100000.ethernet eth0: transmit timed out
Sun Oct  4 19:34:24 2020 kern.info kernel: [   97.402746] mtk_soc_eth 10100000.ethernet eth0: dma_cfg:00000055
Sun Oct  4 19:34:24 2020 kern.info kernel: [   97.408863] mtk_soc_eth 10100000.ethernet eth0: tx_ring=0, base=02cec000, max=1024, ctx=85, dtx=85, fdx=47, next=85
Sun Oct  4 19:34:24 2020 kern.info kernel: [   97.419464] mtk_soc_eth 10100000.ethernet eth0: rx_ring=0, base=02cc8000, max=1024, calc=319, drx=322
3

Can you tell us make/model of router and exact version of OpenWrt is installed?

Unlikely those miniupnpd errors are the cause, but I could be wrong.
If in doubt, I believe you can turn off uPnP functionality in LuCI. (Some software/apps may require uPnP to function correctly)

The problem is if a router does reboot spontaneously, any actual error, if it is even recorded in the System log, is lost.

You would need a serial connection wired to the router's circuit board to try and capture all console messages. But this is only useful if the error is displayed.

Usual non-software causes include an ageing router, or it may be overheating. A failing power adapter which cannot deliver enough power to the router when demanded is another common reason.

4

TP Link Archer C20 V4 running v19.07 of OpenWRT Firmware.

This does not happen when light browsing occurs (i.e. spontaneous shutdown). It's only when I have online classes does this shutdown occurs.

5

Did you previously run an earlier version of OpenWrt?

Are you able to disable wifi on the C20, and test with just ethernet wired connections?

The C20 v4 is a Mediatek MT7628AN device. You may have to wait and see if another C20 owner reports same issue.

6

Yeah, I did. 19.03. I haven't tested yet ethernet, but I will.

7

Open a ssh terminal and run logread -f. This will cause the router to send logs in real time to the PC. Watch for any log messages made shortly before the router crashes. (Note some ssh clients will close the window when the connection dies-- do not use one of those).

2 Likes
8

It was the miniupnpd errors causing such disruptions. Apparently, when I changed the UPnP and Port Forwards to the internal address 192.168.0.0/16, there are no longer any form of disruptions.

Perhaps that address automatically factors in any device that may possess 192.168.x.x hence why the issue being completely sidestepped.

1 Like
9

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.