MT-2500 WAN interface crashes during reading from the Samba server

RRoommaann · 2023-10-11T19:24:45.809Z

Hello everyone!
On my MT-2500, the WAN interface crashes when reading large files from the Samba server. Accordingly, there is no internet connection, and the device is not accessible remotely. After the file copying is completed, everything returns to normal.
What could be causing this issue? The logs are provided below. If more information is needed, please don’t hesitate to ask.

Thanks!

Logs:

Wed Oct 11 19:50:29 2023 daemon.err nmbd[5903]:   *****
Wed Oct 11 19:50:29 2023 daemon.err nmbd[5903]:
Wed Oct 11 19:50:29 2023 daemon.err nmbd[5903]:   Samba name server GL-MT2500 is now a local master browser for workgroup WORKGROUP on subnet 192.168.10.1
Wed Oct 11 19:50:29 2023 daemon.err nmbd[5903]:
Wed Oct 11 19:50:29 2023 daemon.err nmbd[5903]:   *****
Wed Oct 11 19:52:14 2023 kern.warn kernel: [  149.033576] ------------[ cut here ]------------
Wed Oct 11 19:52:14 2023 kern.info kernel: [  149.038202] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 0 timed out
Wed Oct 11 19:52:14 2023 kern.warn kernel: [  149.045188] WARNING: CPU: 0 PID: 0 at dev_watchdog+0x2d8/0x2e0
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.051004] Modules linked in: pppoe ppp_async option wireguard usb_wwan rndis_host qmi_wwan pppox ppp_generic libchacha20poly1305 ipt_REJECT huawei_cdc_ncm chacha_neon cdc_ncm cdc_ether xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_quota xt_pkttype xt_owner 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_addrtype xt_TCPMSS xt_REDIRECT xt_MASQUERADE xt_LOG xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY usbserial usbnet slhc poly1305_neon nf_reject_ipv4 nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_conntrack_netlink nf_conncount mtqos mtfwd libcurve25519_generic libcrc32c libchacha iptable_raw iptable_nat iptable_mangle iptable_filter ipt_ECN ipheth ip_tables exfat crc_ccitt cdc_wdm cdc_acm arptable_filter arpt_mangle arp_tables fuse sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_tcindex cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.051101]  act_gact xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6t_NPT nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 nfsv4 nfsd nfs ifb ip6_udp_tunnel udp_tunnel rpcsec_gss_krb5 auth_rpcgss oid_registry veth tun vfat fat ntfs lockd sunrpc grace dns_resolver dm_mirror dm_region_hash dm_log dm_crypt dm_mod dax nls_utf8 nls_iso8859_1 nls_cp437 md5 des_generic libdes cts cbc arc4 mtdoops leds_gpio uhci_hcd ohci_platform ohci_hcd fsl_mph_dr_of ehci_platform ehci_fsl ehci_hcd gpio_button_hotplug gl_sdk4_tertf gl_sdk4_black_white_list f2fs ext4 mbcache jbd2 mii crc32c_generic crc32_generic gl_sdk4_hw_info
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.224755] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.211 #0
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.230744] Hardware name: GL.iNet GL-MT2500 (DT)
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.235434] pstate: 40000005 (nZcv daif -PAN -UAO)
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.240213] pc : dev_watchdog+0x2d8/0x2e0
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.244211] lr : dev_watchdog+0x2d8/0x2e0
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.248205] sp : ffffffc010003db0
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.251506] x29: ffffffc010003db0 x28: 0000000000000140
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.256804] x27: 00000000ffffffff x26: 0000000000000000
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.262100] x25: 0000000000000000 x24: 0000000000000000
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.267397] x23: 0000000000000001 x22: ffffff8003340000
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.272694] x21: ffffff8003340480 x20: ffffffc010a16000
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.277990] x19: 0000000000000000 x18: 0000000000000000
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.283287] x17: 0000000000000000 x16: 0000000000000000
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.288584] x15: 0000000000000000 x14: ffffffc010a8e39a
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.293882] x13: 0000000000000000 x12: ffffffc010a8d000
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.299179] x11: ffffffc010a26000 x10: 0000000000000010
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.304477] x9 : 0000000000000000 x8 : 75712074696d736e
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.309773] x7 : 617274203a296874 x6 : 0000000000000001
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.315070] x5 : 0000000000000000 x4 : 0000000000000000
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.320366] x3 : 0000000000000000 x2 : ffffff803fdc8260
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.325664] x1 : ffffffc02f3c5000 x0 : 000000000000003f
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.330960] Call trace:
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.333398]  dev_watchdog+0x2d8/0x2e0
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.337048]  call_timer_fn.isra.37+0x20/0x78
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.341304]  run_timer_softirq+0x1e0/0x468
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.345388]  __do_softirq+0x124/0x260
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.349038]  irq_exit+0xb8/0xc8
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.352169]  __handle_domain_irq+0x64/0xb8
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.356251]  gic_handle_irq+0xc0/0x158
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.359988]  el1_irq+0xb8/0x140
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.363118]  arch_cpu_idle+0x10/0x18
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.366683]  do_idle+0x120/0x148
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.369899]  cpu_startup_entry+0x24/0x60
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.373810]  rest_init+0xb0/0xbc
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.377026]  arch_call_rest_init+0xc/0x14
Wed Oct 11 19:52:14 2023 kern.debug kernel: [  149.381022]  start_kernel+0x3f8/0x410
Wed Oct 11 19:52:14 2023 kern.warn kernel: [  149.384671] ---[ end trace 5a71444e6e1db9aa ]---
Wed Oct 11 19:52:14 2023 kern.err kernel: [  149.389311] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Wed Oct 11 19:52:14 2023 kern.info kernel: [  149.396660] [mtk_pending_work] No need to do FE reset !
Wed Oct 11 19:52:20 2023 kern.err kernel: [  154.917097] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Wed Oct 11 19:52:20 2023 kern.info kernel: [  154.923466] [mtk_pending_work] No need to do FE reset !
Wed Oct 11 19:52:25 2023 user.info mwan3track[8909]: Lost 6 ping(s) on interface wan (pppoe-wan)
Wed Oct 11 19:52:56 2023 kern.err kernel: [  191.011367] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Wed Oct 11 19:52:56 2023 kern.info kernel: [  191.017661] [mtk_pending_work] No need to do FE reset !
Wed Oct 11 19:52:57 2023 daemon.err transmission-daemon[7408]: [2023-10-11 19:52:57.739] DHT dht.transmissionbt.com:6881: Try again (tr-dht.c:136)
Wed Oct 11 19:53:01 2023 kern.err kernel: [  196.131595] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Wed Oct 11 19:53:01 2023 kern.info kernel: [  196.137812] [mtk_pending_work] No need to do FE reset !
Wed Oct 11 19:53:07 2023 kern.err kernel: [  202.019813] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Wed Oct 11 19:53:07 2023 kern.info kernel: [  202.026030] [mtk_pending_work] No need to do FE reset !
Wed Oct 11 19:53:18 2023 kern.err kernel: [  213.028227] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Wed Oct 11 19:53:18 2023 kern.info kernel: [  213.034517] [mtk_pending_work] No need to do FE reset !
Wed Oct 11 19:53:26 2023 user.info mwan3track[8909]: Lost 10 ping(s) on interface wan (pppoe-wan)
Wed Oct 11 19:53:35 2023 daemon.info avahi-daemon[3871]: Joining mDNS multicast group on interface zt3jn3vpqc.IPv4 with address 10.10.8.1.
Wed Oct 11 19:53:35 2023 daemon.info avahi-daemon[3871]: New relevant interface zt3jn3vpqc.IPv4 for mDNS.
Wed Oct 11 19:53:35 2023 daemon.info avahi-daemon[3871]: Registering new address record for 10.10.8.1 on zt3jn3vpqc.IPv4.
Wed Oct 11 19:54:48 2023 user.info : luci: accepted login on / for root from 10.10.8.2
Wed Oct 11 20:08:29 2023 kern.err kernel: [ 1123.918631] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Wed Oct 11 20:08:29 2023 kern.info kernel: [ 1123.924940] [mtk_pending_work] No need to do FE reset !
Wed Oct 11 20:08:46 2023 kern.err kernel: [ 1140.812020] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Wed Oct 11 20:08:46 2023 kern.info kernel: [ 1140.818500] [mtk_pending_work] No need to do FE reset !
Wed Oct 11 20:08:56 2023 kern.err kernel: [ 1150.794480] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Wed Oct 11 20:08:56 2023 kern.info kernel: [ 1150.800759] [mtk_pending_work] No need to do FE reset !
Wed Oct 11 20:09:07 2023 kern.err kernel: [ 1161.800847] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Wed Oct 11 20:09:07 2023 kern.info kernel: [ 1161.807073] [mtk_pending_work] No need to do FE reset !
Wed Oct 11 20:09:12 2023 user.info mwan3track[8909]: Lost 11 ping(s) on interface wan (pppoe-wan)

SimBot · 2023-10-12T02:41:54.331Z

Thank you for your feedback, we will record and test it.

ywp · 2023-10-13T02:37:19.633Z

Could you please briefly describe the operating steps and environment? (For example, what format is the USB disk, how big is the file, etc.) We need to reproduce it here

RRoommaann · 2023-10-13T10:19:06.870Z

Hi @ywp,

I’m using the following configuration:

On the MT-2500 router, firmware version 4.4.6 release1 is installed.

The Samba v4 server is running with the standard packages: samba4-libs, samba4-server, samba4-utils from Gl-inet without any modifications.

An SSD with a capacity of 256 GB and an ext4 file system is used for storage:

/dev/sda3: UUID="271fa112-6d67-4026-a9af-0cda3be1917b" VERSION="1.0" MOUNT="/tmp/mountd/disk1_part1" TYPE="ext4"

My SSD contains video files in formats such as avi, mkv, and some iso files with various images. File sizes range from 500 MB to 2 GB.

Copying takes place within LAN. My GL-AR300M with firmware 4.3.7 release1 in Access Point mode is connected to the LAN port of the MT-2500. Client devices are connected to the GL-AR300M via Wi-Fi and Ethernet.

The first occurrence of this problem happened during the copying of an ISO image of approximately 1.2 GB in size. After the problem occurred, for testing purposes, I tried copying several mkv and avi files to a PC running Windows 11 connected to the GL-AR300M via Ethernet.

I noticed that the availability of the router and connected devices on the local network is related to the time it takes to copy files. In other words, the larger the file size, the longer the MT-2500 and client devices on the local network remain inaccessible from the outside world via SSH and RDP.

After several tests, I sent you those logs.

At the same time, I have a DLNA server running that uses the same SSD. The amount of RAM used by my MT-2500 is consistently around 98-99%.

If you need additional information, please don’t hesitate to ask.

Thank you.

glinoob · 2023-10-16T16:20:34.520Z

Try updating to 4.4.6 release2:

Brume 2 firmware update 4.4.6 Technical Support for Routers

[4.4.6 update] Brume 2 firmware update 4.4.6 not working for me. Reset to factory is not working to Back to 4.4.5 no problems

ikun · 2023-10-17T06:54:43.441Z

Hi,
Could you export log and post it to me?

RRoommaann · 2023-10-18T07:32:18.719Z

Hi there,

I tried testing with the latest beta version 4.4.6 a couple of days ago, but it didn’t produce any results; the issue persisted. I flashed it through uboot mode without restoring backups after flashing.

Today I will attempt to test with the new stable firmware version 4.4.6.

@ikun I sent you the logs in a private message.