WRT32X - Snapshot - backtrace

Here is a backtrack of an OOps I found on a syslog server. This device is setup as an Access Point. Would be nice if I could try to prevent iptables/netfilter from loading, but everytime I try the device hangs. I did not try to "rmmod xxxx" for this to show up..

Device: wrt32x
OpenWrt SNAPSHOT r11083-8cb13f4e6d
LuCI Master (git-19.263.54698-720df98)

Trace

Sep 22 10:55:24 xxx kernel: [  300.152392] ------------[ cut here ]------------
Sep 22 10:55:24 xxxkernel: [  300.157046] WARNING: CPU: 1 PID: 215 at net/netfilter/core.c:398 __nf_unregister_net_hook+0x6c/0x180
Sep 22 10:55:24 xxx kernel: [  300.166231] Modules linked in: pppoe ppp_async iptable_nat ipt_MASQUERADE xt_state xt_nat xt_conntrack xt_REDIRECT xt_FLOWOFFLOAD xt_CT pppox ppp_generic nf_nat_ipv4 nf_nat nf_flow_table_hw nf_flow_table nf_conntrack_rtcache nf_conntrack ipt_REJECT xt_time xt_tcpudp xt_multiport xt_mark xt_mac xt_limit xt_comment xt_TCPMSS xt_LOG slhc rfcomm nf_reject_ipv4 nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 mwifiex_sdio mwifiex iptable_mangle iptable_filter ip_tables hidp hci_uart crc_ccitt btusb btmrvl_sdio btmrvl btintel bnep bluetooth hid evdev input_core mwlwifi mac80211 cfg80211 compat nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 msdos vfat fat nls_utf8 nls_iso8859_1 nls_cp437 ecdh_generic sha512_generic sha256_generic seqiv jitterentropy_rng
Sep 22 10:55:24 xxx kernel: [  300.237193]  drbg md5 md4 kpp hmac ecb ctr cmac ccm gpio_button_hotplug
Sep 22 10:55:24 xxx kernel: [  300.243856] CPU: 1 PID: 215 Comm: kworker/u4:3 Not tainted 4.19.74 #0
Sep 22 10:55:24 xxx kernel: [  300.250323] Hardware name: Marvell Armada 380/385 (Device Tree)
Sep 22 10:55:24 xxx kernel: [  300.256273] Workqueue: netns cleanup_net
Sep 22 10:55:24 txxx kernel: [  300.260220] [<c010ebac>] (unwind_backtrace) from [<c010ad10>] (show_stack+0x10/0x14)
Sep 22 10:55:24xxx kernel: [  300.267999] [<c010ad10>] (show_stack) from [<c06b90f0>] (dump_stack+0x88/0x9c)
Sep 22 10:55:24 xxx kernel: [  300.275256] [<c06b90f0>] (dump_stack) from [<c0126188>] (__warn+0xd4/0xf0)
Sep 22 10:55:24 xxx kernel: [  300.282162] [<c0126188>] (__warn) from [<c0126274>] (warn_slowpath_null+0x40/0x48)
Sep 22 10:55:24 xxx kernel: [  300.289768] [<c0126274>] (warn_slowpath_null) from [<c05e0538>] (__nf_unregister_net_hook+0x6c/0x180)
Sep 22 10:55:24xxx kernel: [  300.299030] [<c05e0538>] (__nf_unregister_net_hook) from [<c05e0788>] (nf_unregister_net_hooks+0x1c/0x34)
Sep 22 10:55:24 xxx kernel: [  300.308640] [<c05e0788>] (nf_unregister_net_hooks) from [<c058f9ec>] (ops_exit_list+0x38/0x60)
Sep 22 10:55:24 xxxxkernel: [  300.317291] [<c058f9ec>] (ops_exit_list) from [<c059054c>] (cleanup_net+0x188/0x2a0)
Sep 22 10:55:24 xxx kernel: [  300.325072] [<c059054c>] (cleanup_net) from [<c013cc74>] (process_one_work+0x298/0x418)
Sep 22 10:55:24 xxx kernel: [  300.333112] [<c013cc74>] (process_one_work) from [<c013d11c>] (worker_thread+0x328/0x54c)
Sep 22 10:55:24 xxx kernel: [  300.341328] [<c013d11c>] (worker_thread) from [<c01427e8>] (kthread+0x14c/0x154)
Sep 22 10:55:24 xxkernel: [  300.348757] [<c01427e8>] (kthread) from [<c01010e8>] (ret_from_fork+0x14/0x2c)
Sep 22 10:55:24 txxx kernel: [  300.356009] Exception stack(0xdec11fb0 to 0xdec11ff8)
Sep 22 10:55:24 xxxkernel: [  300.361082] 1fa0:                                     00000000 00000000 00000000 00000000
Sep 22 10:55:24 xxx kernel: [  300.369295] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Sep 22 10:55:24 xxxx kernel: [  300.377508] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
Sep 22 10:55:24 xxx kernel: [  300.384167] ---[ end trace d00eb30f0eddd2a8 ]---

The last image that ran reliably on a rango for me was Sep 13 11:26 r11006-713561a10b, failing in different ways. Interestingly, the same builds that fail on the rango run without issue on a mamba.