OpenWrt 24.10.0-rc7 - Seventh Release Candidate

Release and security announcements
123

For rc7 there are package build errors for banana pi r3 that weren't there on rc6, namely strongswan and "all" the perl packages.

    perl                         Thu Jan 30 07:59:40 2025 - not installed
    perl-authen-sasl-xs          Thu Jan 30 08:04:52 2025 - not installed
    perl-compress-bzip2          Thu Jan 30 08:00:33 2025 - not installed
    perl-dbi                     Thu Jan 30 08:00:34 2025 - not installed
    perl-device-serialport       Thu Jan 30 08:00:33 2025 - not installed
    perl-device-usb              Thu Jan 30 08:01:01 2025 - not installed
    perl-file-rsyncp             Thu Jan 30 08:00:31 2025 - not installed
    perl-html-parser             Thu Jan 30 08:00:56 2025 - not installed
    perl-text-csv_xs             Thu Jan 30 08:00:36 2025 - not installed
    perl-time-moment             Thu Jan 30 08:00:37 2025 - not installed
    perl-www-curl                Thu Jan 30 08:00:37 2025 - not installed
    perl-xml-parser              Thu Jan 30 08:00:37 2025 - not installed
    strongswan                   Thu Jan 30 08:08:06 2025 - not installed
  Feed: telephony
    freeswitch                   Thu Jan 30 08:25:09 2025 - not installed
    freeswitch-mod-bcg729        Thu Jan 30 08:27:08 2025 - not installed
    freetdm                      Thu Jan 30 08:27:08 2025 - not installed

kr

1 Like
124

It happened in the main branch after 24.10 branched off. I wouldn't expect it to come to stable until the next major release series after 24.10, which would be 25.xx.

https://openwrt.org/about/history#branch_logic

125

Thanks - I did a factory reset and applied all settings again and all is working great now. I think I was unable to access the router because the dnsmasq, firewall and odhcpd startup scripts were re-enabled after upgrading.

126

not sure it works like that in practice, as some selected fixes are ported from main into release branch - but let's see :slight_smile:

127

Exactly the same behaviour on a TP-Link Archer C2600:

Sat Feb  1 10:59:09 2025 kern.warn kernel: [   35.560748] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Sat Feb  1 10:59:09 2025 kern.warn kernel: [   35.564339] ------------[ cut here ]------------
Sat Feb  1 10:59:09 2025 kern.warn kernel: [   35.575353] WARNING: CPU: 0 PID: 1140 at backports-6.12.6/net/mac80211/main.c:272 0xbf20b85c [mac80211@4c6ec2bc+0x77000]

It goes away when switching to ath10k (non ct).

EDIT: This is known to be harmless since half a year. See comment to #15959. I switched back to ath10k-ct, and will ignore this warning.

3 Likes
128

Yesterday I've upgraded my ER-X to rc2 and later to rc7 version.
Now I can see someting strange in LOG:

Sat Feb  1 12:25:16 2025 kern.info kernel: [46660.824728] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:25:16 2025 kern.info kernel: [46660.824824] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:25:16 2025 kern.info kernel: [46660.850656] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:25:16 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:25:17 2025 kern.info kernel: [46661.176086] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:25:17 2025 kern.info kernel: [46661.186533] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:25:17 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:25:20 2025 kern.info kernel: [46664.659946] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:25:20 2025 kern.info kernel: [46664.660043] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:25:20 2025 kern.info kernel: [46664.685869] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:25:20 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:25:21 2025 kern.info kernel: [46665.011567] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:25:21 2025 kern.info kernel: [46665.022064] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:25:21 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:25:25 2025 kern.info kernel: [46668.972130] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:25:25 2025 kern.info kernel: [46668.987754] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:25:25 2025 kern.info kernel: [46668.998194] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:25:25 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:27:47 2025 kern.info kernel: [46811.883858] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:27:47 2025 kern.info kernel: [46811.894309] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:27:47 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:27:52 2025 kern.info kernel: [46816.577016] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:27:52 2025 kern.info kernel: [46816.592633] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:27:52 2025 kern.info kernel: [46816.603072] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:27:52 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:27:52 2025 kern.info kernel: [46816.928645] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:27:52 2025 kern.info kernel: [46816.939155] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:27:52 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:27:56 2025 kern.info kernel: [46820.465828] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:27:56 2025 kern.info kernel: [46820.465935] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:27:56 2025 kern.info kernel: [46820.491752] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:27:56 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:27:58 2025 kern.info kernel: [46822.556273] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:27:58 2025 kern.info kernel: [46822.566730] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:27:58 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:28:01 2025 kern.info kernel: [46825.482836] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:28:01 2025 kern.info kernel: [46825.482936] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:28:01 2025 kern.info kernel: [46825.508760] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:28:01 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:28:43 2025 kern.info kernel: [46867.863770] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:28:43 2025 kern.info kernel: [46867.874279] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:28:43 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:28:47 2025 kern.info kernel: [46870.952034] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:28:47 2025 kern.info kernel: [46870.960005] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:28:47 2025 kern.info kernel: [46870.977923] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:28:47 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:29:10 2025 kern.info kernel: [46894.632144] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:29:10 2025 kern.info kernel: [46894.642617] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:29:10 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:29:13 2025 kern.info kernel: [46897.787500] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:29:13 2025 kern.info kernel: [46897.787603] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:29:13 2025 kern.info kernel: [46897.813430] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:29:13 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:29:25 2025 kern.info kernel: [46909.404741] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:29:25 2025 kern.info kernel: [46909.415235] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:29:25 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:29:28 2025 kern.info kernel: [46912.367095] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:29:28 2025 kern.info kernel: [46912.380089] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:29:28 2025 kern.info kernel: [46912.392967] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:29:28 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:29:29 2025 kern.info kernel: [46913.910879] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:29:29 2025 kern.info kernel: [46913.921384] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:29:29 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:29:33 2025 kern.info kernel: [46916.980468] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:29:33 2025 kern.info kernel: [46916.983794] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:29:33 2025 kern.info kernel: [46917.006380] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:29:33 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:29:33 2025 kern.info kernel: [46917.790775] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:29:33 2025 kern.info kernel: [46917.801229] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:29:33 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:29:40 2025 kern.info kernel: [46924.484312] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:29:40 2025 kern.info kernel: [46924.499932] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:29:40 2025 kern.info kernel: [46924.510402] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:29:40 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:29:41 2025 kern.info kernel: [46925.780631] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:29:41 2025 kern.info kernel: [46925.791052] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:29:41 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:29:44 2025 kern.info kernel: [46928.906860] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:29:44 2025 kern.info kernel: [46928.906957] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:29:44 2025 kern.info kernel: [46928.932777] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:29:44 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:29:45 2025 kern.info kernel: [46929.258846] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:29:45 2025 kern.info kernel: [46929.269287] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:29:45 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:29:52 2025 kern.info kernel: [46935.971732] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:29:52 2025 kern.info kernel: [46935.971828] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:29:52 2025 kern.info kernel: [46935.997661] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:29:52 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:29:52 2025 kern.info kernel: [46936.725947] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:29:52 2025 kern.info kernel: [46936.736407] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:29:52 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 12:29:55 2025 kern.info kernel: [46939.907694] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 12:29:55 2025 kern.info kernel: [46939.920156] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 12:29:55 2025 kern.info kernel: [46939.933559] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 12:29:55 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 12:29:56 2025 kern.info kernel: [46940.607792] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 12:29:56 2025 kern.info kernel: [46940.618293] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 12:29:56 2025 daemon.notice netifd: Network device 'eth1' link is down

I don't know why... but I lost my LAN connection on eth1. On 23.05.5 version does not to do that.

129

@lexmark3200 There is a known 24.10 ramips issue that may be mitigated by disabling EEE. You'll use more Watts, but until it's fixed, try:

opkg update
opkg install ethtool
ethtool --show-eee eth1
ethtool --set-eee eth1 eee off
ethtool --show-eee eth1

You'll need to add the ethtool EEE disable command to /etc/rc.local for it to persist on each bootup.

3 Likes
130

Ok thx, for your reply.

root@Router:~# ethtool --show-eee eth1
EEE Settings for eth1:
        EEE status: enabled - inactive
        Tx LPI: 30 (us)
        Supported EEE link modes:  100baseT/Full
                                   1000baseT/Full
        Advertised EEE link modes:  100baseT/Full
                                    1000baseT/Full
        Link partner advertised EEE link modes:  Not reported
root@Router:~# ethtool --set-eee eth1 eee off
root@Router:~# ethtool --show-eee eth1
EEE Settings for eth1:
        EEE status: disabled
        Tx LPI: 30 (us)
        Supported EEE link modes:  100baseT/Full
                                   1000baseT/Full
        Advertised EEE link modes:  Not reported
        Link partner advertised EEE link modes:  Not reported
root@Router:~#
131

Hi, I report back after testing upgrade on an Archer C6 V2 EU running 23.05.5, all upgrades were made with settings kept:

  1. Created two images for 24.05.5 and 24.10.0-rc7 with openwrt firmware selector (there are not many packages added besides batman and auc)
  2. Tried upgrade via auc -b 24.10, and answered with "yes" to all modifications required for transition. Got build fail with following error: "Error: Impossible package selection: owut version not as requested: 2025.01.25~2bf45d50-r1 vs. 2025.01.29~bced54ad-r1".
  3. Tried upgrade with the 24.10 image created at point 1 above (not via auc). Upgraded successfully, but 5GHz issue was there, applied workaround from @zekica and restored 5GHz wifi.
  4. Returned to 23.05.5 with the image at point 1 (downgrade to stable)
  5. Tried again upgrade as done at point 2 above, but forced with auc -f -b 24.10 and answered "yes" to all transition request required but with "NO" to the replacement of package auc with owut (since it was the one blocking upgrade at point 2). Upgraded successfully but with the same 5GHz issue which needed workaround to solve.

Conclusion: on my Archer C6 V2 EU the 5GHz issue is confirmed and for me remains a mystery how it could go without issue for @d687r02j8g. Thank you !

132

I have Netgear switch GS724v4 with EEE on, maybe this is the problem too. To eth2 on er-x I have connected the second switch Netgear GS108 but without EEE, and there is no problem with DW/UP link. :thinking:

133

I no longer use ramips targets on my network, but FWIW, on my GS308T switch running 24.10rc7, ethtool reports EEE is not supported on lan1 and disabled by default on lan2-lan7.

134

Strange. I just double checked my router and the 5ghz is definitely up!

root@archera6:~# iwinfo
phy0-ap0  ESSID: "<ssid>"
          Access Point: mac
          Mode: Master  Channel: 36 (5.180 GHz)  HT Mode: HT40
          Center Channel 1: 38 2: unknown
          Tx-Power: 23 dBm  Link Quality: 63/70
          Signal: -47 dBm  Noise: -112 dBm
          Bit Rate: 360.0 MBit/s
          Encryption: WPA2 PSK (CCMP)
          Type: nl80211  HW Mode(s): 802.11ac/n
          Hardware: 168C:0056 0000:0000 [Qualcomm Atheros QCA9886]
          TX power offset: none
          Frequency offset: none
          Supports VAPs: yes  PHY name: phy0

root@archera6:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='24.10.0-rc7'
DISTRIB_REVISION='r28417-daef29c75d'
DISTRIB_TARGET='ath79/generic'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt 24.10.0-rc7 r28417-daef29c75d'
DISTRIB_TAINTS=''

root@archera6:~# ifconfig phy0-ap0
phy0-ap0  Link encap:Ethernet  HWaddr <Mac>
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:948 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2440 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:128215 (125.2 KiB)  TX bytes:3093112 (2.9 MiB)

From the kernel log, not sure if it's relevant

[  732.256411] ath10k_pci 0000:00:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[  732.264261] ath10k_pci 0000:00:00.0: msdu-desc: 2500  skid: 32
[  732.314421] ath10k_pci 0000:00:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
[  732.315258] ath10k_pci 0000:00:00.0: wmi print 'free: 114572 iram: 12644 sram: 29508'
[  732.622172] ath10k_pci 0000:00:00.0: rts threshold -1
[  732.622671] ath10k_pci 0000:00:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[  732.634141] ------------[ cut here ]------------
[  732.638917] WARNING: CPU: 0 PID: 1609 at backports-6.12.6/net/mac80211/main.c:272 0x8292089c [mac80211@7f0ffe3a+0x8a000]
[  732.650207] Modules linked in: ath9k(O) ath9k_common(O) pppoe ppp_async nft_fib_inet nf_flow_table_inet ath9k_hw(O) ath10k_pci(O) ath10k_core(O) ath(O) pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota 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_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mac80211(O) cfg80211(O) slhc nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c hwmon crc_ccitt compat(O) sha512_generic seqiv sha3_generic jitterentropy_rng drbg hmac geniv rng cmac gpio_button_hotplug(O) crc32c_generic
[  732.712163] CPU: 0 PID: 1609 Comm: hostapd Tainted: G        W  O       6.6.73 #0
[  732.719898] Stack : 00000000 8075832c 00000000 82bacea8 00000000 00000000 00000000 00000000
[  732.728551]         00000000 00000000 00000000 00000000 00000000 00000001 81ae9b10 13691ace
[  732.737206]         81ae9ba8 00000000 00000000 81ae9a58 00000038 80701424 00000000 ffffffea
[  732.745861]         00000134 81ae9a64 00000134 807f9720 8071a9b8 81ae9af0 00000000 8292089c
[  732.754517]         00000009 82bacea8 00000000 82d33500 00000018 803d09c8 00000000 809b0000
[  732.763172]         ...
[  732.765700] Call Trace:
[  732.765823] [<80701424>] 0x80701424
[  732.772017] [<8292089c>] 0x8292089c [mac80211@7f0ffe3a+0x8a000]
[  732.778214] [<803d09c8>] 0x803d09c8
[  732.781900] [<800661e8>] 0x800661e8
[  732.785502] [<800661f0>] 0x800661f0
[  732.789103] [<806d7da8>] 0x806d7da8
[  732.792732] [<800849b0>] 0x800849b0
[  732.796390] [<8292089c>] 0x8292089c [mac80211@7f0ffe3a+0x8a000]
[  732.802549] [<80084a40>] 0x80084a40
[  732.806195] [<82902394>] 0x82902394 [mac80211@7f0ffe3a+0x8a000]
[  732.812458] [<8292089c>] 0x8292089c [mac80211@7f0ffe3a+0x8a000]
[  732.818763] [<82920a60>] 0x82920a60 [mac80211@7f0ffe3a+0x8a000]
[  732.825012] [<804bc974>] 0x804bc974
[  732.828698] [<804bce8c>] 0x804bce8c
[  732.832434] [<804bcf38>] 0x804bcf38
[  732.836062] [<800be27c>] 0x800be27c
[  732.839691] [<804b0d30>] 0x804b0d30
[  732.843320] [<805a84f4>] 0x805a84f4
[  732.846948] [<8048a628>] 0x8048a628
[  732.850607] [<805ab230>] 0x805ab230
[  732.854314] [<804ee854>] 0x804ee854
[  732.857970] [<804ef63c>] 0x804ef63c
[  732.861626] [<8048adcc>] 0x8048adcc
[  732.865390] [<8048c39c>] 0x8048c39c
[  732.869046] [<80221310>] 0x80221310
[  732.872726] [<80488dd8>] 0x80488dd8
[  732.876382] [<8048cb54>] 0x8048cb54
[  732.879984] [<80488fa8>] 0x80488fa8
[  732.883645] [<8006d420>] 0x8006d420
[  732.887314] 
[  732.889002] ---[ end trace 0000000000000000 ]---
[  732.905455] br-lan: port 2(phy0-ap0) entered blocking state
[  732.905487] br-lan: port 2(phy0-ap0) entered disabled state
[  732.905534] ath10k_pci 0000:00:00.0 phy0-ap0: entered allmulticast mode
[  732.905810] ath10k_pci 0000:00:00.0 phy0-ap0: entered promiscuous mode
1 Like
135

I have d-link dir 878, 2660 and 2150 with the same CPU mt7621 as er-x but there is no issue, maybe becouse there wiek as AP only...

The questions is, should I off EEE on rest of ports (eth2 and eth3) on er-x ?

136

I tested RC7 unfortunately/fortunately (depends on ones perspective ... since I can not reproduce LAN drop issue) I do not see any issues on my NanoPi R4S devices:

  • This time installed both the squashfs and ext4 variant.
  • It booted on "normal" R4S and on the Enterprise edition (to clarify, I own both devices, actually three of them).
  • In each test, I rebooted the devices 3 times ... so in total 12 reboots, 6 on each device, since I gave squashfs and ext4 a try.
  • Result: Boots normally for me, I do not see LAN drops after reboot.
137

3-4h later still issue present, with eee off:

root@Router:~# ethtool --show-eee eth1
EEE Settings for eth1:
        EEE status: disabled
        Tx LPI: 30 (us)
        Supported EEE link modes:  100baseT/Full
                                   1000baseT/Full
        Advertised EEE link modes:  Not reported
        Link partner advertised EEE link modes:  Not reported
root@Router:~#


Sat Feb  1 15:52:16 2025 kern.info kernel: [59080.151284] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 15:52:16 2025 kern.info kernel: [59080.157599] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 15:52:16 2025 kern.info kernel: [59080.177187] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 15:52:16 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb  1 15:52:16 2025 kern.info kernel: [59080.686334] mt7530-mdio mdio-bus:1f eth1: Link is Down
Sat Feb  1 15:52:16 2025 kern.info kernel: [59080.696790] br-lan: port 1(eth1) entered disabled state
Sat Feb  1 15:52:16 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb  1 15:52:19 2025 kern.info kernel: [59083.645386] mt7530-mdio mdio-bus:1f eth1: Link is Up - 1Gbps/Full - flow control off
Sat Feb  1 15:52:19 2025 kern.info kernel: [59083.645477] br-lan: port 1(eth1) entered blocking state
Sat Feb  1 15:52:19 2025 kern.info kernel: [59083.671309] br-lan: port 1(eth1) entered forwarding state
Sat Feb  1 15:52:19 2025 daemon.notice netifd: Network device 'eth1' link is upde here

Now I disabled Auto Power Down Mode on Netgear GS724Tv4.

update:
After a few minutes the same issue :confused:

1 Like
138

Can this be added to the wiki, or will it be patched in Stable release?

Edit: didn't seem to resolve the issue. :frowning:

139

This issue is still open.

140

TY, will follow it there.

141

This is curious because I have d-link dir 878, 2660 and 2150 with the same CPU MT7621 and the issue is absent.
From my dir-878:

root@AP4:~# ubus call system board
{
        "kernel": "6.6.73",
        "hostname": "AP4",
        "system": "MediaTek MT7621 ver:1 eco:3",
        "model": "D-Link DIR-878 A1",
        "board_name": "dlink,dir-878-a1",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.0-rc7",
                "revision": "r28417-daef29c75d",
                "target": "ramips/mt7621",
                "description": "OpenWrt 24.10.0-rc7 r28417-daef29c75d",
                "builddate": "1738018409"
        }
}

root@AP4:~# ethtool --show-eee lan1
EEE Settings for lan1:
        EEE status: enabled - active
        Tx LPI: 30 (us)
        Supported EEE link modes:  100baseT/Full
                                   1000baseT/Full
        Advertised EEE link modes:  100baseT/Full
                                    1000baseT/Full
        Link partner advertised EEE link modes:  100baseT/Full
                                    1000baseT/Full
142

As always, "It depends." What's your use case?

  • I like GUI and don't want to bother with fancy options or crossing release boundaries: Use LuCI Attended Sysupgrade.
  • I want off-device generation and manual control of packages: Use Firmware Selector.
  • I like the command line and finer control of packages and image parameters: Use owut.
  • I like command line, but I'm on 23.05 or older: Use auc.
2 Likes