[19.07.3-EA8500] Is this a bug?

Hello,

I frequently have this entry in dmesg output:

[51483.633121] ------------[ cut here ]------------
[51483.633195] WARNING: CPU: 1 PID: 3120 at backports-4.19.120-1/net/wireless/util.c:1147 0xbf41fd88 [cfg80211@bf41b000+0x37000]
[51483.638091] invalid rate bw=0, mcs=15, nss=4
[51483.648900] Modules linked in: pppoe ppp_async option ath10k_pci ath10k_core ath usb_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cypress_m8 cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT usbserial ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda 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 nf_conntrack iptable_mangle iptable_filter ip_tables crc_ccitt compat ledtrig_usbport nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT
[51483.701534]  x_tables nf_reject_ipv6 nfsv4 nfsv3 nfs rpcsec_gss_krb5 auth_rpcgss oid_registry tun lockd sunrpc grace dns_resolver dm_mirror dm_region_hash dm_log dm_crypt dm_mod dax sha1_generic md5 ecb des_generic cts cbc uas usb_storage f2fs ext4 mbcache jbd2 crc32c_generic crc32_generic leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_of_simple ohci_platform ohci_hcd phy_qcom_dwc3 ahci ehci_platform sd_mod ahci_platform libahci_platform libahci libata scsi_mod ehci_hcd gpio_button_hotplug
[51483.745084] CPU: 1 PID: 3120 Comm: hostapd Not tainted 4.14.180 #0
[51483.767201] Hardware name: Generic DT based system
[51483.773460] Function entered at [<c030f1c4>] from [<c030b390>]
[51483.778227] Function entered at [<c030b390>] from [<c07c09c4>]
[51483.784045] Function entered at [<c07c09c4>] from [<c031f878>]
[51483.789860] Function entered at [<c031f878>] from [<c031f8d8>]
[51483.795677] Function entered at [<c031f8d8>] from [<bf41fd88>]
[51483.801570] Function entered at [<bf41fd88>] from [<bf42d83c>]
[51483.807317] Function entered at [<bf42d83c>] from [<bf43a654>]
[51483.813128] Function entered at [<bf43a654>] from [<bf43b248>]
[51483.818943] Function entered at [<bf43b248>] from [<bf475b68>]
[51483.824800] Function entered at [<bf475b68>] from [<bf475bfc>]
[51483.830574] Function entered at [<bf475bfc>] from [<bf475c94>]
[51483.836390] Function entered at [<bf475c94>] from [<bf4296d8>]
[51483.842209] Function entered at [<bf4296d8>] from [<c06e1a1c>]
[51483.848022] Function entered at [<c06e1a1c>] from [<c06e0238>]
[51483.853835] Function entered at [<c06e0238>] from [<c06e0a10>]
[51483.859650] Function entered at [<c06e0a10>] from [<c06dfa48>]
[51483.865465] Function entered at [<c06dfa48>] from [<c06dfe64>]
[51483.871284] Function entered at [<c06dfe64>] from [<c0689d5c>]
[51483.877100] Function entered at [<c0689d5c>] from [<c068a5c4>]
[51483.882915] Function entered at [<c068a5c4>] from [<c0307b60>]
[51483.888867] ---[ end trace 5b14df2e4b515b88 ]---

Device data:

Model Linksys EA8500 WiFi Router
Architecture  ARMv7 Processor rev 0 (v7l)
Firmware Version OpenWrt 19.07.3 r11063-85e04e9f46 / LuCI openwrt-19.07 branch git-20.136.49537-fb2f363
Kernel Version 4.14.180

I looked into the project bug reporting page, but I admit I was a bit overwhelmed as I'm no developer and wasn't sure if it was the right thing to do...

My release is currently 19.07.3. Would it be worth to upgrade to the latest 19.07.6 ?
I took a look into the release notes and the only update for the EA8500 was on 19.07.4 (some boot partition fix), so not sure if it would help...

Cheers,
Jabss

Yes, it is a kernel oops and shouldn't happen. Your wireless driver (brcmfmac) apparently triggers an issue in the wireless stack, apparently while reporting the current wireless link rate (as a fullmac driver, there might not be that much reporting, as the firmware is doing the rate control itself).

Personally I'd first check a current master/ snapshot build, to check if the issue is still present there.