Belkin RT3200/Linksys E8450 WiFi AX discussion

Anteus · October 15, 2022, 8:07pm

For 3. Belkin RT3200/Linksys E8450 WiFi AX discussion - #1775 by hnyman

ismail · October 16, 2022, 6:48am

Is there any update on the 00-prefer-libwolfsslcpu-crypto plan? That sounds like a good workaround to this issue. Thanks!

umayer · October 16, 2022, 7:55am

@daniel
since you asked for it...

The dumps were collected on 09/23. I don't know whether they are still useful as they are 3 weeks old by now and I don't recall the exact git hash:
dmesg-ramoops-0

<6>[    8.278919] Backport generated by backports.git v5.15.58-1-0-g42a95ce7
<7>[    8.348438] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
<7>[    8.359648] mt7915e 0000:01:00.0: assign IRQ: got 150
<7>[    8.364811] pci 0000:00:00.0: enabling bus mastering
<6>[    8.369793] mt7915e 0000:01:00.0: enabling device (0000 -> 0002)
<7>[    8.375924] mt7915e 0000:01:00.0: enabling bus mastering
<6>[    8.402814] mt7622-wmac 18000000.wmac: HW/SW Version: 0x8a108a10, Build Time: 20190801210006a
<6>[    8.402814] 
<6>[    8.487977] mt7622-wmac 18000000.wmac: N9 Firmware Version: _reserved_, Build Time: 20220630094834
<6>[    8.568237] mt7915e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20211222184017a
<6>[    8.568237] 
<6>[    8.696599] mt7915e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20211222184052
<6>[    8.753585] mt7915e 0000:01:00.0: WA Firmware Version: DEV_000000, Build Time: 20211222184111
<6>[    8.902108] PPP generic driver version 2.4.2
<6>[    8.909472] NET: Registered protocol family 24
<14>[    8.917925] kmodloader: done loading kernel modules from /etc/modules.d/*
<6>[   11.620624] mtk_soc_eth 1b100000.ethernet eth0: Link is Down
<6>[   11.631418] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode
<6>[   11.640320] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
<6>[   11.649131] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
<6>[   11.657806] mt7530 mdio-bus:00 lan1: configuring for phy/gmii link mode
<6>[   11.665384] 8021q: adding VLAN 0 to HW filter on device lan1
<6>[   11.676097] br-lan: port 1(lan1) entered blocking state
<6>[   11.681336] br-lan: port 1(lan1) entered disabled state
<6>[   11.690194] device lan1 entered promiscuous mode
<6>[   11.694869] device eth0 entered promiscuous mode
<6>[   11.708840] mt7530 mdio-bus:00 lan2: configuring for phy/gmii link mode
<6>[   11.716172] 8021q: adding VLAN 0 to HW filter on device lan2
<6>[   11.720450] mt7530 mdio-bus:00 lan2: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[   11.724208] br-lan: port 2(lan2) entered blocking state
<6>[   11.734648] br-lan: port 2(lan2) entered disabled state
<6>[   11.740660] device lan2 entered promiscuous mode
<6>[   11.754563] mt7530 mdio-bus:00 lan3: configuring for phy/gmii link mode
<6>[   11.761793] 8021q: adding VLAN 0 to HW filter on device lan3
<6>[   11.766455] mt7530 mdio-bus:00 lan3: Link is Up - 100Mbps/Full - flow control off
<6>[   11.769770] br-lan: port 3(lan3) entered blocking state
<6>[   11.780208] br-lan: port 3(lan3) entered disabled state
<6>[   11.786452] device lan3 entered promiscuous mode
<6>[   11.800006] mt7530 mdio-bus:00 lan4: configuring for phy/gmii link mode
<6>[   11.807236] 8021q: adding VLAN 0 to HW filter on device lan4
<6>[   11.815236] br-lan: port 4(lan4) entered blocking state
<6>[   11.820471] br-lan: port 4(lan4) entered disabled state
<6>[   11.826888] device lan4 entered promiscuous mode
<6>[   11.840568] mt7530 mdio-bus:00 wan: configuring for phy/gmii link mode
<6>[   11.847799] 8021q: adding VLAN 0 to HW filter on device wan
<6>[   11.857991] mt7530 mdio-bus:00 wan: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[   11.867916] br-lan: port 5(wan) entered blocking state
<6>[   11.873129] br-lan: port 5(wan) entered disabled state
<6>[   11.879585] device wan entered promiscuous mode
<6>[   11.897090] br-lan: port 5(wan) entered blocking state
<6>[   11.902275] br-lan: port 5(wan) entered forwarding state
<6>[   11.907676] br-lan: port 3(lan3) entered blocking state
<6>[   11.912942] br-lan: port 3(lan3) entered forwarding state
<6>[   11.918442] br-lan: port 2(lan2) entered blocking state
<6>[   11.923712] br-lan: port 2(lan2) entered forwarding state
<6>[   14.158662] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
<6>[   14.377778] mt7530 mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[   14.385424] br-lan: port 1(lan1) entered blocking state
<6>[   14.390657] br-lan: port 1(lan1) entered forwarding state
<6>[   14.582186] br-lan: port 6(wlan0) entered blocking state
<6>[   14.587514] br-lan: port 6(wlan0) entered disabled state
<6>[   14.593174] device wlan0 entered promiscuous mode
<6>[   14.598072] br-lan: port 6(wlan0) entered blocking state
<6>[   14.603447] br-lan: port 6(wlan0) entered forwarding state
<6>[   14.855515] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<6>[   15.367034] br-lan: port 7(wlan1) entered blocking state
<6>[   15.372491] br-lan: port 7(wlan1) entered disabled state
<6>[   15.378211] device wlan1 entered promiscuous mode
<6>[   15.383344] br-lan: port 7(wlan1) entered blocking state
<6>[   15.388672] br-lan: port 7(wlan1) entered forwarding state
<6>[   15.394785] br-lan: port 7(wlan1) entered disabled state
<6>[   16.200760] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
<6>[   16.207425] br-lan: port 7(wlan1) entered blocking state
<6>[   16.212854] br-lan: port 7(wlan1) entered forwarding state
<6>[   16.256444] br-lan: port 8(wlan1-1) entered blocking state
<6>[   16.261999] br-lan: port 8(wlan1-1) entered disabled state
<6>[   16.267798] device wlan1-1 entered promiscuous mode
<6>[   16.277186] br-lan: port 8(wlan1-1) entered blocking state
<6>[   16.282724] br-lan: port 8(wlan1-1) entered forwarding state
<6>[   16.294173] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready
<1>[78596.451785] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d8
<1>[78596.460656] Mem abort info:
<1>[78596.463461]   ESR = 0x96000005
<1>[78596.466569]   EC = 0x25: DABT (current EL), IL = 32 bits
<1>[78596.472013]   SET = 0, FnV = 0
<1>[78596.475067]   EA = 0, S1PTW = 0
<1>[78596.478271] Data abort info:
<1>[78596.481162]   ISV = 0, ISS = 0x00000005
<0>[78596.483803] usercopy: Kernel memory exposure attempt detected from SLUB object 'kmalloc-512' (offset 116, size 131068)!
<1>[78596.484996]   CM = 0, WnR = 0
<1>[78596.485006] user pgtable: 4k pages, 39-bit VAs, pgdp=0000000041401000
<1>[78596.485013] [00000000000000d8] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000
<0>[78596.485036] Internal error: Oops: 96000005 [#1] SMP
<7>[78596.485041] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mt7915e mt7615e mt7615_common mt76_connac_lib mt76 mac80211 cfg80211 slhc nfnetlink nf_reject_ipv6 nf_reject_ipv4
<7>[78596.496197] ------------[ cut here ]------------
<7>[78596.498958]  nf_log_ipv6
<2>[78596.505398] Kernel BUG at 0xffffffc0107f6380 [verbose debug info unavailable]
<7>[78596.514080]  nf_log_ipv4 nf_log_common nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c hwmon crc_ccitt compat seqiv leds_gpio xhci_plat_hcd gpio_button_hotplug
<7>[78596.592498] CPU: 1 PID: 1003 Comm: ubusd Tainted: G S                5.10.143 #0
<7>[78596.599890] Hardware name: Linksys E8450 (UBI) (DT)
<7>[78596.604772] pstate: 20000005 (nzCv daif -PAN -UAO -TCO BTYPE=--)
<7>[78596.610777] pc : 0xffffffc01016ff34
<7>[78596.614265] lr : 0xffffffc01016fec0
<7>[78596.617750] sp : ffffffc0110bb960
<7>[78596.621062] x29: ffffffc0110bb960 x28: 0000000000400cc0 
<7>[78596.626382] x27: 0000000000000003 x26: 0000000000000000 
<7>[78596.631702] x25: ffffffc0110bbbac x24: ffffffc01006ccd0 
<7>[78596.637022] x23: 0000000000400cc0 x22: ffffffc0109f8000 
<7>[78596.642341] x21: 0000000000000000 x20: 0000000000400cc0 
<7>[78596.647660] x19: ffffff8000025a00 x18: 0000000000000000 
<7>[78596.652979] x17: 0000000000000000 x16: 0000000000000000 
<7>[78596.658298] x15: 0000005565b17140 x14: 0000000000000000 
<7>[78596.663616] x13: 0000000000000000 x12: 0000000000000000 
<7>[78596.668934] x11: 0000000000000000 x10: 000000007ffff000 
<7>[78596.674253] x9 : 0000000000000000 x8 : 0000007f8b400140 
<7>[78596.679572] x7 : 0000000000000060 x6 : ffffffc0110bbcc0 
<7>[78596.684890] x5 : 0000000000000003 x4 : fffffffeffe22040 
<7>[78596.690210] x3 : ffffffc0109ea4d0 x2 : 0000000000000070 
<7>[78596.695528] x1 : 0000000000000068 x0 : 000000000246b444 
<7>[78596.700846] Call trace:
<7>[78596.703294]  0xffffffc01016ff34
<7>[78596.706434]  0xffffffc01063800c
<7>[78596.709575]  0xffffffc01063f34c
<7>[78596.712714]  0xffffffc010633190
<7>[78596.715853]  0xffffffc01075ec6c
<7>[78596.718992]  0xffffffc01062cc10
<7>[78596.722132]  0xffffffc01062ff68
<7>[78596.725272]  0xffffffc010630034
<7>[78596.728411]  0xffffffc0106300a0
<7>[78596.731551]  0xffffffc010010f30
<7>[78596.734691]  0xffffffc010010ffc
<7>[78596.737831]  0xffffffc0107fcb74
<7>[78596.740970]  0xffffffc0107fcf90
<7>[78596.744110]  0xffffffc0100025c8
<0>[78596.747261] Code: f100009f fa401824 540009c0 b9402a62 (f8626822) 
<4>[78596.753355] ---[ end trace f316a9ee5e8304d0 ]---

and
dmesg-ramoops-1

<7>[    8.375924] mt7915e 0000:01:00.0: enabling bus mastering
<6>[    8.402814] mt7622-wmac 18000000.wmac: HW/SW Version: 0x8a108a10, Build Time: 20190801210006a
<6>[    8.402814] 
<6>[    8.487977] mt7622-wmac 18000000.wmac: N9 Firmware Version: _reserved_, Build Time: 20220630094834
<6>[    8.568237] mt7915e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20211222184017a
<6>[    8.568237] 
<6>[    8.696599] mt7915e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20211222184052
<6>[    8.753585] mt7915e 0000:01:00.0: WA Firmware Version: DEV_000000, Build Time: 20211222184111
<6>[    8.902108] PPP generic driver version 2.4.2
<6>[    8.909472] NET: Registered protocol family 24
<14>[    8.917925] kmodloader: done loading kernel modules from /etc/modules.d/*
<6>[   11.620624] mtk_soc_eth 1b100000.ethernet eth0: Link is Down
<6>[   11.631418] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode
<6>[   11.640320] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
<6>[   11.649131] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
<6>[   11.657806] mt7530 mdio-bus:00 lan1: configuring for phy/gmii link mode
<6>[   11.665384] 8021q: adding VLAN 0 to HW filter on device lan1
<6>[   11.676097] br-lan: port 1(lan1) entered blocking state
<6>[   11.681336] br-lan: port 1(lan1) entered disabled state
<6>[   11.690194] device lan1 entered promiscuous mode
<6>[   11.694869] device eth0 entered promiscuous mode
<6>[   11.708840] mt7530 mdio-bus:00 lan2: configuring for phy/gmii link mode
<6>[   11.716172] 8021q: adding VLAN 0 to HW filter on device lan2
<6>[   11.720450] mt7530 mdio-bus:00 lan2: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[   11.724208] br-lan: port 2(lan2) entered blocking state
<6>[   11.734648] br-lan: port 2(lan2) entered disabled state
<6>[   11.740660] device lan2 entered promiscuous mode
<6>[   11.754563] mt7530 mdio-bus:00 lan3: configuring for phy/gmii link mode
<6>[   11.761793] 8021q: adding VLAN 0 to HW filter on device lan3
<6>[   11.766455] mt7530 mdio-bus:00 lan3: Link is Up - 100Mbps/Full - flow control off
<6>[   11.769770] br-lan: port 3(lan3) entered blocking state
<6>[   11.780208] br-lan: port 3(lan3) entered disabled state
<6>[   11.786452] device lan3 entered promiscuous mode
<6>[   11.800006] mt7530 mdio-bus:00 lan4: configuring for phy/gmii link mode
<6>[   11.807236] 8021q: adding VLAN 0 to HW filter on device lan4
<6>[   11.815236] br-lan: port 4(lan4) entered blocking state
<6>[   11.820471] br-lan: port 4(lan4) entered disabled state
<6>[   11.826888] device lan4 entered promiscuous mode
<6>[   11.840568] mt7530 mdio-bus:00 wan: configuring for phy/gmii link mode
<6>[   11.847799] 8021q: adding VLAN 0 to HW filter on device wan
<6>[   11.857991] mt7530 mdio-bus:00 wan: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[   11.867916] br-lan: port 5(wan) entered blocking state
<6>[   11.873129] br-lan: port 5(wan) entered disabled state
<6>[   11.879585] device wan entered promiscuous mode
<6>[   11.897090] br-lan: port 5(wan) entered blocking state
<6>[   11.902275] br-lan: port 5(wan) entered forwarding state
<6>[   11.907676] br-lan: port 3(lan3) entered blocking state
<6>[   11.912942] br-lan: port 3(lan3) entered forwarding state
<6>[   11.918442] br-lan: port 2(lan2) entered blocking state
<6>[   11.923712] br-lan: port 2(lan2) entered forwarding state
<6>[   14.158662] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
<6>[   14.377778] mt7530 mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[   14.385424] br-lan: port 1(lan1) entered blocking state
<6>[   14.390657] br-lan: port 1(lan1) entered forwarding state
<6>[   14.582186] br-lan: port 6(wlan0) entered blocking state
<6>[   14.587514] br-lan: port 6(wlan0) entered disabled state
<6>[   14.593174] device wlan0 entered promiscuous mode
<6>[   14.598072] br-lan: port 6(wlan0) entered blocking state
<6>[   14.603447] br-lan: port 6(wlan0) entered forwarding state
<6>[   14.855515] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<6>[   15.367034] br-lan: port 7(wlan1) entered blocking state
<6>[   15.372491] br-lan: port 7(wlan1) entered disabled state
<6>[   15.378211] device wlan1 entered promiscuous mode
<6>[   15.383344] br-lan: port 7(wlan1) entered blocking state
<6>[   15.388672] br-lan: port 7(wlan1) entered forwarding state
<6>[   15.394785] br-lan: port 7(wlan1) entered disabled state
<6>[   16.200760] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
<6>[   16.207425] br-lan: port 7(wlan1) entered blocking state
<6>[   16.212854] br-lan: port 7(wlan1) entered forwarding state
<6>[   16.256444] br-lan: port 8(wlan1-1) entered blocking state
<6>[   16.261999] br-lan: port 8(wlan1-1) entered disabled state
<6>[   16.267798] device wlan1-1 entered promiscuous mode
<6>[   16.277186] br-lan: port 8(wlan1-1) entered blocking state
<6>[   16.282724] br-lan: port 8(wlan1-1) entered forwarding state
<6>[   16.294173] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready
<1>[78596.451785] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d8
<1>[78596.460656] Mem abort info:
<1>[78596.463461]   ESR = 0x96000005
<1>[78596.466569]   EC = 0x25: DABT (current EL), IL = 32 bits
<1>[78596.472013]   SET = 0, FnV = 0
<1>[78596.475067]   EA = 0, S1PTW = 0
<1>[78596.478271] Data abort info:
<1>[78596.481162]   ISV = 0, ISS = 0x00000005
<0>[78596.483803] usercopy: Kernel memory exposure attempt detected from SLUB object 'kmalloc-512' (offset 116, size 131068)!
<1>[78596.484996]   CM = 0, WnR = 0
<1>[78596.485006] user pgtable: 4k pages, 39-bit VAs, pgdp=0000000041401000
<1>[78596.485013] [00000000000000d8] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000
<0>[78596.485036] Internal error: Oops: 96000005 [#1] SMP
<7>[78596.485041] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mt7915e mt7615e mt7615_common mt76_connac_lib mt76 mac80211 cfg80211 slhc nfnetlink nf_reject_ipv6 nf_reject_ipv4
<7>[78596.496197] ------------[ cut here ]------------
<7>[78596.498958]  nf_log_ipv6
<2>[78596.505398] Kernel BUG at 0xffffffc0107f6380 [verbose debug info unavailable]
<7>[78596.514080]  nf_log_ipv4 nf_log_common nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c hwmon crc_ccitt compat seqiv leds_gpio xhci_plat_hcd gpio_button_hotplug
<7>[78596.592498] CPU: 1 PID: 1003 Comm: ubusd Tainted: G S                5.10.143 #0
<7>[78596.599890] Hardware name: Linksys E8450 (UBI) (DT)
<7>[78596.604772] pstate: 20000005 (nzCv daif -PAN -UAO -TCO BTYPE=--)
<7>[78596.610777] pc : 0xffffffc01016ff34
<7>[78596.614265] lr : 0xffffffc01016fec0
<7>[78596.617750] sp : ffffffc0110bb960
<7>[78596.621062] x29: ffffffc0110bb960 x28: 0000000000400cc0 
<7>[78596.626382] x27: 0000000000000003 x26: 0000000000000000 
<7>[78596.631702] x25: ffffffc0110bbbac x24: ffffffc01006ccd0 
<7>[78596.637022] x23: 0000000000400cc0 x22: ffffffc0109f8000 
<7>[78596.642341] x21: 0000000000000000 x20: 0000000000400cc0 
<7>[78596.647660] x19: ffffff8000025a00 x18: 0000000000000000 
<7>[78596.652979] x17: 0000000000000000 x16: 0000000000000000 
<7>[78596.658298] x15: 0000005565b17140 x14: 0000000000000000 
<7>[78596.663616] x13: 0000000000000000 x12: 0000000000000000 
<7>[78596.668934] x11: 0000000000000000 x10: 000000007ffff000 
<7>[78596.674253] x9 : 0000000000000000 x8 : 0000007f8b400140 
<7>[78596.679572] x7 : 0000000000000060 x6 : ffffffc0110bbcc0 
<7>[78596.684890] x5 : 0000000000000003 x4 : fffffffeffe22040 
<7>[78596.690210] x3 : ffffffc0109ea4d0 x2 : 0000000000000070 
<7>[78596.695528] x1 : 0000000000000068 x0 : 000000000246b444 
<7>[78596.700846] Call trace:
<7>[78596.703294]  0xffffffc01016ff34
<7>[78596.706434]  0xffffffc01063800c
<7>[78596.709575]  0xffffffc01063f34c
<7>[78596.712714]  0xffffffc010633190
<7>[78596.715853]  0xffffffc01075ec6c
<7>[78596.718992]  0xffffffc01062cc10
<7>[78596.722132]  0xffffffc01062ff68
<7>[78596.725272]  0xffffffc010630034
<7>[78596.728411]  0xffffffc0106300a0
<7>[78596.731551]  0xffffffc010010f30
<7>[78596.734691]  0xffffffc010010ffc
<7>[78596.737831]  0xffffffc0107fcb74
<7>[78596.740970]  0xffffffc0107fcf90
<7>[78596.744110]  0xffffffc0100025c8
<0>[78596.747261] Code: f100009f fa401824 540009c0 b9402a62 (f8626822) 
<4>[78596.753355] ---[ end trace f316a9ee5e8304d0 ]---
<0>[78596.776887] Kernel panic - not syncing: Oops: Fatal exception
<2>[78596.782639] SMP: stopping secondary CPUs
<4>[78597.921225] SMP: failed to stop secondary CPUs 0-1
<0>[78597.926013] Kernel Offset: disabled
<0>[78597.929501] CPU features: 0x00000002,04002004
<0>[78597.933854] Memory Limit: none

diff between the two:

diff --git a/network/bug/dmesg-ramoops-0 b/network/bug/dmesg-ramoops-1
index a7c1e75..a366cc9 100644
--- a/network/bug/dmesg-ramoops-0
+++ b/network/bug/dmesg-ramoops-1
@@ -1,9 +1,4 @@
-Oops#1 Part1
-<6>[    8.278919] Backport generated by backports.git v5.15.58-1-0-g42a95ce7
-<7>[    8.348438] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
-<7>[    8.359648] mt7915e 0000:01:00.0: assign IRQ: got 150
-<7>[    8.364811] pci 0000:00:00.0: enabling bus mastering
-<6>[    8.369793] mt7915e 0000:01:00.0: enabling device (0000 -> 0002)
+Panic#2 Part1
 <7>[    8.375924] mt7915e 0000:01:00.0: enabling bus mastering
 <6>[    8.402814] mt7622-wmac 18000000.wmac: HW/SW Version: 0x8a108a10, Build Time: 20190801210006a
 <6>[    8.402814] 
@@ -135,3 +130,9 @@ Oops#1 Part1
 <7>[78596.744110]  0xffffffc0100025c8
 <0>[78596.747261] Code: f100009f fa401824 540009c0 b9402a62 (f8626822) 
 <4>[78596.753355] ---[ end trace f316a9ee5e8304d0 ]---
+<0>[78596.776887] Kernel panic - not syncing: Oops: Fatal exception
+<2>[78596.782639] SMP: stopping secondary CPUs
+<4>[78597.921225] SMP: failed to stop secondary CPUs 0-1
+<0>[78597.926013] Kernel Offset: disabled
+<0>[78597.929501] CPU features: 0x00000002,04002004
+<0>[78597.933854] Memory Limit: none

Btw:
A big Thank You. I have replaced all my Archer C7 with the Belkin rt3200.
It is really great to see the active development and caring community which already yielded in a rock solid router/AP.
Here they are running just fine with DAWN, wireguard VPN, Adblock, SQM, VLANs.
Even the latest features work reasonably well: I enabled WED with bridger on the APs. Performance rocks allthough mobile devices end up with wifi connected but no internet sometimes until I reboot an AP

Thank you also to you @darksky for updating

hnyman · October 16, 2022, 8:33am

First guess is some pointer error in the driver, where the main pointer variable is 0 (wrong), and just the data structure offset d8 gets added to the 0.

74hct04 · October 16, 2022, 11:23am

Is there an easy way to move from SNAPSHOT - r20813-3968529285 to 23.03.2 please?

Honestly, I am very confused. AUC is offering only 23.03.1 and looks like it would need to downgrade various componets if I took it (which would make sense). ASU is only offering further snapshots.

At the time of writing https://git.openwrt.org/?p=openwrt/openwrt.git;a=shortlog;h=refs/heads/openwrt-22.03 suggests that 22.03.2 is the very latest build (more recent than the latest snapshot -
SNAPSHOT (r20954-cb24be47ff) ) but I don't know if I can / should switch to it. I think it's time to move away from snapshots as major fixes get backported to the releases? Am I getting this all wrong?

I am still very confused about the various OpenWrt branches but I'd like to update my platform without reinstalling and reconfiguring packages from scratch.

By the way, this is still a test router so I don't mind some cutting edge / bleeding edge risk...

hnyman · October 16, 2022, 11:27am

Well, you are now in the development master, and you seem to want to downgrade into the stable release branch 22.03 (mainly from 2002 March + bug fixes).

See this:

74hct04 · October 16, 2022, 11:31am

Thank you for your reply.

Well, you are now in the development master, and you seem to want to downgrade into the stable release branch 22.03 (mainly from 2002 March + bug fixes).

Oh, am I? I thought the development master - specifically I mean this https://git.openwrt.org/?p=openwrt/openwrt.git;a=shortlog;h=refs/heads/master , was something I could only compile/build myself? Now I'm even more confused!

hnyman · October 16, 2022, 11:34am

No, the "snaphosts" are daily made from all active branches (master, 22.03 and 21.02). The SNAPSHOT by itself does not yet specify the branch.

Master snapshots are offered by the page (for the enthusiasts) while the release branch snapshots are somewhat hidden.

https://downloads.openwrt.org/

Ps.

22.03 snapshots:

https://downloads.openwrt.org/releases/22.03-SNAPSHOT/

74hct04 · October 16, 2022, 11:38am

Thank you. I'm starting to understand this better. Perhaps I will start again running stable releases on the spare RT3200 I have (which is still running stock firmware).

I recently been using ASU to perform the upgrades, after first checking that the one I'm about to install is the latest snapshot listed here https://firmware-selector.openwrt.org/

Ps.

22.03 snapshots:

https://downloads.openwrt.org/releases/22.03-SNAPSHOT/

So am I right in thinking that if I switched from SNAPSHOT - r20813-3968529285 to these 22.03 snapshots somehow, files on my RT3200 may be newer than those included in the 22.03 snapshots?

If I understand correctly, thesee 22.03 snapshots are not the nightly snapshots I am currently running one of!

hnyman · October 16, 2022, 11:54am

You sound confused. ¨
22.03 snapshots are newer than 22.03 snapshots?
(But if you meant your currently running master snapshot, then yes, many files there are newer than those in the 22.03 snapshots or 22.03.2 release)

Basically, unless you are compiling from sources by yourself, think that "snapshots" seen in firmware selector, auc etc. are from master, while the static releases (like 22.03.2) are from the release branches like 22.03.

If you want an easy life, just stick to the 22.03 releases. (22.03.2 was tagged yesterday and is currently being compiled in buildbot)

(But this whole discussion has nothing to do with RT3200 specifically, so rather off-topic here.)

lamelogin · October 17, 2022, 12:51pm

@hnyman, how should toggle_bootcmd be invoked? Is this something that needs to be run only once at install/upgrade time? Where/how should this be invoked? is /etc/rc.local sufficient?

Anteus · October 17, 2022, 1:10pm

Once or until you flash the bootloader again.

daniel · October 17, 2022, 1:10pm

As the setting is stored in the persistent U-Boot environment you can use the script only to change the dual-boot behavior. No need to call it more than once, after upgrades or even on every boot.

cotequeiroz · October 17, 2022, 1:59pm

TLDR: I proposed a proper resolution for it here: https://gitlab.com/openwrt/project/opkg-lede/-/merge_requests/1 but it has not received any attention, apparently.

Instead of a workaround, I went all in with a proper fix in opkg. The problem started when an ABI version string was added to library packages, to avoid ABI breakage. So the official name of the libwolfssl package became libwolfssl5.5.1.b24d5f87, and libwolfssl was added to the package's provide list. When you run opkg install libustream-wolfssl, for example, opkg will see it has a ´libwolfssldependency. It will search through the list of packages providinglibwolfssl`, giving preference to the ones that match any cmdline argument. Since libwolfssl will not match any package name, it will resort to alphabetical order.

If you add libwolfssl-cpu-crypto5.5.1.b24d5f87 anywere in the cmdline, then it will be given preference over libwolfssl5.5.1.b24d5f87 because it was found in the cmdline.

If you add plain libwolfssl-cpu-crypto, it will not match the package's name and will not be chosen. Order is relevant because if libwolfss-cpu-crypto were installed before libustream-ssl, then the search will not be done. We can't change the order, nor use the package with the ABI, because the firmware builder strips any abi info and sorts the list of packages, to avoid generation of duplicate images.

The proper fix is to change opkg to give priority to packages whose ABI-stripped name matches any package in the command line. This will restore the behavior it had before the ABI version naming was introduced.

Since this change affects a major piece of the infrastructure, I expect more scrutiny before a merge, but it has not received any feedback or an indication that anyone is looking into this .

daniel · October 17, 2022, 2:01pm

That's because this is the wrong place to submit it. We don't use gitlab.com, but the plan to maybe do so did exist in the past. Please report to the mailing list and prefix the subject with opkg: .

Trinity · October 17, 2022, 4:47pm

Newbie question here

I am following the official guide for installing openwrt on RT3200. In the step "Enable WED", it states that I need to

Edit /etc/modules.conf and append this line: options mt7915e wed_enable=Y

However, this file does not exist on my openwrt so I tried to create the file and add the line, but after reboot and checking with cat /sys/module/mt7915e/parameters/wed_enable I get N

Am I doing something wrong here and why does /etc/modules.conf not exist on my installation?

p.s. I am running 22.03.1

urbenlegend · October 17, 2022, 6:10pm

Thanks for the tip on how to set boot envs.

Still unclear about how to flash a new recovery image. Do I boot into the recovery OS and flash linksys_e8450-ubi-initramfs-recovery.itb?

hnyman · October 17, 2022, 7:11pm

I am still not sure why you would need/want to to replace the recovery image.
It is mostly(only) meant as a flashing tool for the actual production image. It should not be used for dual-boot purposes.

Daniek has given advice earlier in this thread:

urbenlegend · October 17, 2022, 9:34pm

Thanks! It was more out of pure curiousity and satisfying my OCD. I don't really plan on using the recovery OS for any other purpose besides flashing. Ideally, I just want official OpenWrt images for everything on my router and I find the switch in the default theme that's used in dangowrt to be a bit jarring when and if my router crashes and goes into recovery mode.

slh · October 18, 2022, 12:30am

The recovery image is your lifeboat, don't touch it unless you really know you need to. If you break it, the router is toast for any userfriendly recovery means (that don't involve soldering and more).