Ubiquiti UniFi AC HD/ipq806x 160mhz support broken?

I've upgraded to 23.05.0 with ipq806x/Ubiquiti UniFi AC HD hardware and it seems that the operation frequency width 160mhz seems to be broken.

When enabling that frequency, logs reports as follows:

Tue Oct 31 19:33:13 2023 daemon.notice hostapd: Set new config for phy phy0:
Tue Oct 31 19:33:13 2023 daemon.notice hostapd: Remove interface 'phy0'
Tue Oct 31 19:33:13 2023 daemon.notice hostapd: phy0-ap0: interface state DISABLED->DISABLED
Tue Oct 31 19:33:13 2023 daemon.notice hostapd: phy0-ap0: AP-DISABLED
Tue Oct 31 19:33:13 2023 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING
Tue Oct 31 19:33:13 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Tue Oct 31 19:33:13 2023 daemon.err hostapd: hostapd_free_hapd_data: Interface phy0-ap0 wasn't started
Tue Oct 31 19:33:13 2023 kern.info kernel: [ 3011.350563] device phy0-ap0 left promiscuous mode
Tue Oct 31 19:33:13 2023 kern.info kernel: [ 3011.350602] br-lan: port 3(phy0-ap0) entered disabled state
Tue Oct 31 19:33:13 2023 daemon.notice wpa_supplicant[1319]: Set new config for phy phy0
Tue Oct 31 19:33:13 2023 daemon.notice netifd: Wireless device 'radio0' is now down
Tue Oct 31 19:33:13 2023 daemon.notice netifd: radio0 (8062): WARNING: Variable 'data' does not exist or is not an array/object
Tue Oct 31 19:33:13 2023 daemon.notice hostapd: Set new config for phy phy0:
Tue Oct 31 19:33:13 2023 daemon.notice wpa_supplicant[1319]: Set new config for phy phy0
Tue Oct 31 19:33:13 2023 daemon.notice wpa_supplicant[1319]: Set new config for phy phy0
Tue Oct 31 19:33:13 2023 daemon.notice hostapd: Set new config for phy phy0: /var/run/hostapd-phy0.conf
Tue Oct 31 19:33:13 2023 daemon.notice hostapd: Restart interface for phy phy0
Tue Oct 31 19:33:13 2023 kern.info kernel: [ 3011.822033] br-lan: port 3(phy0-ap0) entered blocking state
Tue Oct 31 19:33:13 2023 kern.info kernel: [ 3011.822064] br-lan: port 3(phy0-ap0) entered disabled state
Tue Oct 31 19:33:13 2023 kern.info kernel: [ 3011.826585] device phy0-ap0 entered promiscuous mode
Tue Oct 31 19:33:13 2023 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 hw_mode=a beacon_int=100 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=2 vht_oper_centr_freq_seg0_idx=acs_survey vht_capab=[RXLDPC][SHORT-GI-80][SHORT-GI-160][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-4][BF-ANTENNA-4][VHT160-80PLUS80][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] channel=acs_survey  interface=phy0-ap0 bssid=[BSSID] ctrl_interface=/var/run/hostapd ap_isolate=1 bss_load_update_period=60 chan_util_avg_period=600 disassoc_low_ack=1 skip_inactivity_poll=0 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 utf8_ssid=1 multi_ap=0 sae_require_mfp=1 sae_pwe=2 wpa_passphrase=z
Tue Oct 31 19:33:13 2023 daemon.notice netifd: Network device 'phy0-ap0' link is up
Tue Oct 31 19:33:16 2023 kern.warn kernel: [ 3014.387135] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
Tue Oct 31 19:33:16 2023 kern.warn kernel: [ 3014.387175] ath10k_pci 0000:01:00.0: msdu-desc: 2500  skid: 32
Tue Oct 31 19:33:16 2023 kern.info kernel: [ 3014.467826] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
Tue Oct 31 19:33:16 2023 kern.info kernel: [ 3014.468646] ath10k_pci 0000:01:00.0: wmi print 'free: 84920 iram: 13156 sram: 11224'
Tue Oct 31 19:33:16 2023 daemon.notice netifd: Network device 'phy0-ap0' link is down
Tue Oct 31 19:33:16 2023 kern.info kernel: [ 3014.845858] ath10k_pci 0000:01:00.0: rts threshold -1
Tue Oct 31 19:33:16 2023 kern.warn kernel: [ 3014.846089] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Tue Oct 31 19:33:16 2023 kern.info kernel: [ 3014.849984] br-lan: port 3(phy0-ap0) entered blocking state
Tue Oct 31 19:33:16 2023 kern.info kernel: [ 3014.860911] br-lan: port 3(phy0-ap0) entered forwarding state
Tue Oct 31 19:33:16 2023 kern.info kernel: [ 3014.866679] br-lan: port 3(phy0-ap0) entered disabled state
Tue Oct 31 19:33:16 2023 daemon.notice hostapd: ACS: Automatic channel selection started, this may take a bit
Tue Oct 31 19:33:16 2023 daemon.notice hostapd: phy0-ap0: interface state UNINITIALIZED->ACS
Tue Oct 31 19:33:16 2023 daemon.notice hostapd: phy0-ap0: ACS-STARTED
Tue Oct 31 19:33:17 2023 daemon.notice netifd: Wireless device 'radio0' is now up

Tue Oct 31 19:33:24 2023 daemon.err hostapd: ACS: Failed to compute ideal channel
Tue Oct 31 19:33:24 2023 daemon.err hostapd: Interface initialization failed
Tue Oct 31 19:33:24 2023 daemon.notice hostapd: phy0-ap0: interface state ACS->DISABLED
Tue Oct 31 19:33:24 2023 daemon.notice hostapd: phy0-ap0: AP-DISABLED
Tue Oct 31 19:33:24 2023 daemon.err hostapd: ACS: Possibly channel configuration is invalid, please report this along with your config file.
Tue Oct 31 19:33:24 2023 daemon.err hostapd: ACS: Failed to start
Tue Oct 31 19:33:24 2023 daemon.notice hostapd: phy0-ap0: AP-DISABLED
Tue Oct 31 19:33:24 2023 daemon.err hostapd: hostapd_free_hapd_data: Interface phy0-ap0 wasn't started
Tue Oct 31 19:33:24 2023 daemon.notice hostapd: nl80211: deinit ifname=phy0-ap0 disabled_11b_rates=0
Tue Oct 31 19:33:24 2023 kern.warn kernel: [ 3022.182439] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
Tue Oct 31 19:33:24 2023 daemon.notice hostapd: phy0-ap0: interface state DISABLED->DISABLED
Tue Oct 31 19:33:24 2023 kern.info kernel: [ 3022.265364] br-lan: port 3(phy0-ap0) entered disabled state

your wireless config file would probably be useful here. Have you set the country code?