几个月前我开始使用 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：
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 不稳定的日志有什么关系吗？
我确实想了解这里发生了什么，并且我阅读了很多论坛，但很难解决。