Hi! The snapshot from yesterday (r27783?) has killed my MT7916 radios (2.5 and 6 GHz).
The errors I get are these ones:
Wed Oct 16 20:06:17 2024 daemon.notice netifd: radio1 (2551): WARNING: Variable 'data' does not exist or is not an array/object
Wed Oct 16 20:06:17 2024 daemon.notice netifd: radio1 (2551): Phy not found
Wed Oct 16 20:06:17 2024 daemon.notice netifd: radio1 (2551): Could not find PHY for device 'radio1'
Wed Oct 16 20:06:17 2024 daemon.notice netifd: radio0 (2550): WARNING: Variable 'data' does not exist or is not an array/object
Wed Oct 16 20:06:17 2024 daemon.notice netifd: Wireless device 'radio1' set retry=0
Wed Oct 16 20:06:17 2024 daemon.crit netifd: Wireless device 'radio1' setup failed, retry=0
Wed Oct 16 20:06:17 2024 daemon.notice netifd: radio0 (2550): Phy not found
Wed Oct 16 20:06:17 2024 daemon.notice netifd: radio0 (2550): Could not find PHY for device 'radio0'
Wed Oct 16 20:06:17 2024 daemon.notice netifd: Wireless device 'radio0' set retry=0
Wed Oct 16 20:06:17 2024 daemon.crit netifd: Wireless device 'radio0' setup failed, retry=0
Wed Oct 16 20:06:17 2024 daemon.notice netifd: radio1 (2622): WARNING: Variable 'data' does not exist or is not an array/object
Wed Oct 16 20:06:17 2024 daemon.notice netifd: radio1 (2622): Bug: PHY is undefined for device 'radio1'
Wed Oct 16 20:06:17 2024 daemon.notice netifd: Wireless device 'radio1' is now down
Wed Oct 16 20:06:17 2024 daemon.notice netifd: radio0 (2633): WARNING: Variable 'data' does not exist or is not an array/object
Wed Oct 16 20:06:17 2024 daemon.notice netifd: radio0 (2633): Bug: PHY is undefined for device 'radio0'
Wed Oct 16 20:06:17 2024 daemon.notice netifd: Wireless device 'radio0' is now down
I didn't have this issue with the snapshot of Oct 10 - I am sorry, I cannot identify the exact snapshot where things stopped working.
With the stable release (23.05.5) the radios work, but with that version I have the issue that when a station disconnects from radio2 (the 5GHz one) I get a kernel panic and the whole stuff reboots (it's this bug). That's why I am "on snapshots"...
Can anyone (@maze ?) help identifying the commit with the regression?
Please... 
Broken snapshot data:
Date of generation: Wed Oct 16 18:24:54 2024
sha256sum:8e0141e532e2de3a9c6979b4a3d94131a8c16d13aecf7ecda5d7a508ac50ff9f