LAN unstable and no WIFI

Installing and Using OpenWrt
1

This my router's specifications:

  • CPU: IPQ6018/AP-CP03-C1 (CpuMark : 20481.310804 Scores)
  • Arch: ARMv8 Processor x 4 (1056MHz, 65.0°C )
  • OS: OpenWrt R22.4.18 / LuCI Master (git-22.106.39772-c3076db)
  • Kernel: 4.4.60

I run the following commands to install some packages:

opkg update
opkg install iperf3 grep

Everything seemed OK. But I typed "reboot" to reboot router. I got the following result:

  • the LAN is unstable.
    I could ssh into the system, do some jobs. Seconds later, the connection was lost. The networking became unstable: normal for seconds -> connection lost for seconds -> noral for seconds -> connection lost for seconds ...
  • No wifi was availabe.

I got some log during the period when the connection is normal:

root@OpenWrt:~# logread -f | tee 2.log
Thu Apr 28 17:49:22 2022 daemon.notice procd: /etc/rc.d/S95shadowsocksr: /etc/rc.common: line 152: flock: not found
Thu Apr 28 17:49:26 2022 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Thu Apr 28 17:49:27 2022 daemon.notice procd: /etc/rc.d/S95shadowsocksr: iptables: Resource temporarily unavailable.
Thu Apr 28 17:49:27 2022 daemon.notice procd: /etc/rc.d/S95shadowsocksr: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?
Thu Apr 28 17:49:28 2022 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Thu Apr 28 17:49:28 2022 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Thu Apr 28 17:49:29 2022 daemon.notice procd: /etc/rc.d/S95shadowsocksr: /etc/rc.common: line 1: flock: not found
Thu Apr 28 17:49:29 2022 cron.info crond[3071]: crond (busybox 1.28.3) started, log level 5
Thu Apr 28 17:49:30 2022 daemon.info qbittorrent: Instance "main" disabled.
Thu Apr 28 17:49:30 2022 daemon.notice procd: /etc/rc.d/S99qbittorrent: Command failed: Invalid argument
Thu Apr 28 17:49:30 2022 daemon.notice ttyd[3185]: ttyd 1.6.3 (libwebsockets 2.4.1)
Thu Apr 28 17:49:30 2022 daemon.notice ttyd[3185]: tty configuration:
Thu Apr 28 17:49:30 2022 daemon.notice ttyd[3185]:   start command: /bin/login
Thu Apr 28 17:49:30 2022 daemon.notice ttyd[3185]:   close signal: SIGHUP (1)
Thu Apr 28 17:49:30 2022 daemon.notice ttyd[3185]:   terminal type: xterm-256color
Thu Apr 28 17:49:30 2022 daemon.notice ttyd[3185]: Creating Vhost 'default' port 7681, 2 protocols, IPv6 off
Thu Apr 28 17:49:30 2022 daemon.notice ttyd[3185]:  Listening on port: 7681
Thu Apr 28 17:49:30 2022 daemon.notice ttyd[3185]:  Using foreign event loop...
Thu Apr 28 17:49:35 2022 daemon.notice procd: /etc/rc.d/S99zerotier: disabled in config
Thu Apr 28 17:49:35 2022 daemon.info procd: - init complete -
Thu Apr 28 17:49:35 2022 kern.err kernel: [   38.854822] cnss[2]: ERR: FW ready timed-out 15 seconds
Thu Apr 28 17:49:35 2022 kern.err kernel: [   38.854849] qmi_history_index [12]
Thu Apr 28 17:49:35 2022 kern.err kernel: [   38.858846] qmi_history[0]:timestamp[22009] instance_id [0x2] msg_id[0x20] err[0] resp_err[0]
Thu Apr 28 17:49:35 2022 kern.err kernel: [   38.862326] qmi_history[1]:timestamp[22009] instance_id [0x2] msg_id[0x20] err[0] resp_err[0]
Thu Apr 28 17:49:35 2022 kern.err kernel: [   38.870948] qmi_history[2]:timestamp[22009] instance_id [0x2] msg_id[0x34] err[0] resp_err[0]
Thu Apr 28 17:49:35 2022 kern.err kernel: [   38.879486] qmi_history[3]:timestamp[22009] instance_id [0x2] msg_id[0x34] err[0] resp_err[0]
Thu Apr 28 17:49:35 2022 kern.err kernel: [   38.887956] qmi_history[4]:timestamp[22026] instance_id [0x2] msg_id[0x35] err[0] resp_err[0]
Thu Apr 28 17:49:36 2022 kern.err kernel: [   38.896464] qmi_history[5]:timestamp[22027] instance_id [0x2] msg_id[0x36] err[0] resp_err[0]
Thu Apr 28 17:49:36 2022 kern.err kernel: [   38.904964] qmi_history[6]:timestamp[22027] instance_id [0x2] msg_id[0x36] err[0] resp_err[0]
Thu Apr 28 17:49:36 2022 kern.err kernel: [   38.913456] qmi_history[7]:timestamp[22027] instance_id [0x2] msg_id[0x37] err[0] resp_err[0]
Thu Apr 28 17:49:36 2022 kern.err kernel: [   38.921991] qmi_history[8]:timestamp[22027] instance_id [0x2] msg_id[0x24] err[0] resp_err[0]
Thu Apr 28 17:49:36 2022 kern.err kernel: [   38.930504] qmi_history[9]:timestamp[22027] instance_id [0x2] msg_id[0x24] err[0] resp_err[0]
Thu Apr 28 17:49:36 2022 kern.err kernel: [   38.939003] qmi_history[10]:timestamp[22027] instance_id [0x2] msg_id[0x25] err[0] resp_err[0]
Thu Apr 28 17:49:36 2022 kern.err kernel: [   38.947500] qmi_history[11]:timestamp[22033] instance_id [0x2] msg_id[0x25] err[0] resp_err[0]
Thu Apr 28 17:49:36 2022 kern.err kernel: [   38.956034] qmi_history[12]:timestamp[22033] instance_id [0x2] msg_id[0x25] err[0] resp_err[0]
Thu Apr 28 17:49:36 2022 kern.err kernel: [   38.964585] cnss[2]: ERR: ASSERT at line 718
Thu Apr 28 17:49:36 2022 kern.warn kernel: [   38.973215] ------------[ cut here ]------------
Thu Apr 28 17:49:37 2022 kern.crit kernel: [   38.977597] kernel BUG at drivers/net/wireless/cnss2/main.c:718!
Thu Apr 28 17:49:37 2022 kern.emerg kernel: [   38.982201] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP

Network error: Software caused connection abort

Could anyone tell me what is the reason, and how to fix the unstable networking?

2

Old (likely unsupported) version of OpenWrt.

SSH in to the router and run ubus call system board or post a screenshot of the main LuCI overview page that shows OpenWrt version.

The kernel for the current release is 5.4.188

3

Please talk to the manufacturer.

OpenWrt doesn't support ipq601x yet, nor has there been anyone working on adding support for it so far - so your issues are with the QSDK based vendor firmware, not OpenWrt. Only they can help you with that.

1 Like
4

The output looks like this:

root@OpenWrt:~#  ubus call system board
{
        "kernel": "4.4.60",
        "hostname": "OpenWrt",
        "model": "360V6 IPQ6018\/AP-CP03-C1",
        "board_name": "ap-cp03-c1",
        "release": {
                "distribution": "LEDE",
                "version": "17.01-SNAPSHOT",
                "target": "ipq60xx\/generic",
                "revision": "R22.4.18",
                "description": "OpenWrt "
        }
}

Er, the kernel and the firmware are too old. I shall talk to the vendor.

Thank you everyone.