Debian SID系统中ath10k_pci固件报错导致WiFi频繁断连重连问题排查求助

几个月前我开始使用Debian SID，每次开机用journalctl -p 3 -xb查看错误日志时，都会看到以下内容：

pcieport 0000:00:1c.5: AER: Error of this Agent is reported first

ath10k_pci 0000:02:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:02:00.0.bin (-2)

ath10k_pci 0000:02:00.0: firmware: failed to load ath10k/cal-pci-0000:02:00.0.bin (-2)

DMAR: DRHD: handling fault status reg 2

DMAR: [DMA Write NO_PASID] Request device [02:00.0] fault addr 0xfefe8000 [fault reason 0x05] PTE Write access is not set

一开始我没把这些报错当回事，日常使用也没遇到明显问题，但最近WiFi开始频繁自动断连重连，我用dmesg -w实时查看内核日志，抓到了这些相关信息：

ath10k_pci 0000:02:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0

wlp2s0: Connection to AP 00:00:00:00:00:00 lost

wlp2s0: authenticate with <macaddress>

wlp2s0: 80 MHz not supported, disabling VHT

wlp2s0: send auth to <macaddress> (try 1/3)

wlp2s0: authenticated

wlp2s0: associate with <macaddress> (try 1/3)

wlp2s0: RX AssocResp from <macaddress> (capab=0x1411 status=30 aid=896)

wlp2s0: <macaddress> rejected association temporarily; comeback duration 1024 TU (1048 ms)

wlp2s0: associate with <macaddress> (try 2/3)

wlp2s0: associate with <macaddress> (try 3/3)

wlp2s0: association with <macaddress> timed out

wlp2s0: authenticate with <macaddress>

wlp2s0: 80 MHz not supported, disabling VHT

wlp2s0: send auth to <macaddress> (try 1/3)

wlp2s0: authenticated

wlp2s0: associate with <macaddress> (try 1/3)

wlp2s0: RX AssocResp from <macaddress> (capab=0x1411 status=0 aid=3)

wlp2s0: associated

同时用journalctl -xfu NetworkManager跟踪NetworkManager状态，也看到了反复的连接状态切换：

device (wlp2s0): supplicant interface state: completed -> disconnected

device (p2p-dev-wlp2s0): supplicant management interface state: completed -> disconnected

device (wlp2s0): supplicant interface state: disconnected -> scanning

device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning

device (wlp2s0): supplicant interface state: scanning -> authenticating

device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating

device (wlp2s0): supplicant interface state: authenticating -> associating

device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating

device (wlp2s0): supplicant interface state: associating -> disconnected

device (p2p-dev-wlp2s0): supplicant management interface state: associating -> disconnected

device (wlp2s0): supplicant interface state: disconnected -> scanning

device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning

device (wlp2s0): supplicant interface state: scanning -> authenticating

device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating

device (wlp2s0): supplicant interface state: authenticating -> associating

device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating

device (wlp2s0): supplicant interface state: associating -> associated

device (p2p-dev-wlp2s0): supplicant management interface state: associating -> associated

device (wlp2s0): supplicant interface state: associated -> 4way_handshake

device (p2p-dev-wlp2s0): supplicant management interface state: associated -> 4way_handshake

device (wlp2s0): supplicant interface state: 4way_handshake -> completed

device (wlp2s0): ip:dhcp4: restarting

dhcp4 (wlp2s0): canceled DHCP transaction

dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)

dhcp4 (wlp2s0): state changed no lease

dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)

device (p2p-dev-wlp2s0): supplicant management interface state: 4way_handshake -> completed

dhcp4 (wlp2s0): state changed new lease, address=<localip>

有没有大佬能给点排查思路？开机时journalctl -p 3 -xb里的那些报错，会不会和现在WiFi不稳定的问题有关？

我已经翻了不少论坛，但还是摸不着头绪，实在是想搞清楚到底哪里出问题了。

备注：内容来源于stack exchange，提问作者rhuanpk