New issue by OrichalcumCosmonaut on void-packages repository

https://github.com/void-linux/void-packages/issues/36447

Description:
### System

* xuname: Void 5.15.32_1 x86_64 GenuineIntel uptodate rrrrmmnFFFF
* package: linux5.15-5.15.32_1

I have a system with a Wi-Fi adapter card `sudo lspci -vvvk` reports as:
```
06:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
	Subsystem: Qualcomm Atheros Device 3112
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 18
	Region 0: Memory at fbdc0000 (64-bit, non-prefetchable) [size=128K]
	Expansion ROM at fbd00000 [virtual] [disabled] [size=64K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
		Address: 0000000000000000  Data: 0000
		Masking: 00000000  Pending: 00000000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <1us, L1 <8us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <2us, L1 <64us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis+ NROPrPrP- LTR-
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp- ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [140 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [300 v1] Device Serial Number 00-00-00-00-00-00-00-00
	Kernel driver in use: ath9k
```

Recently (like, yesterday or the day before), I rebooted my system after it was up for (I think) about a month, and found that the wireless stopped working very well.  It regularly reconnects while under use, and stutters for about 10-15 seconds while reconnecting sometimes too.  A process named `ksoftirqd/4` also uses about 30% of a CPU according to `top` while this happens, suggesting it may be getting stuck in a loop on something.  However, it was working before, and if I boot with `linux-lts` (`linux5.10`) instead, it works normally.  Other devices using Wi-Fi in my house, like my phone, also work normally.

Things like this also appear in the output of `sudo dmesg -H`, which I assume isn’t normal:
```
[Apr 1 10:14] wlp6s0: authenticate with <modem MAC address>
[  +0.013816] wlp6s0: send auth to <modem MAC address> (try 1/3)
[  +0.002412] wlp6s0: authenticated
[  +0.001021] wlp6s0: associate with <modem MAC address> (try 1/3)
[  +0.004568] wlp6s0: RX AssocResp from <modem MAC address> (capab=0x411 status=0 aid=33)
[  +0.000098] wlp6s0: associated
[  +0.015766] wlp6s0: Limiting TX power to 36 (36 - 0) dBm as advertised by <modem MAC address>
[Apr 1 10:22] wlp6s0: disassociated from <modem MAC address> (Reason: 5=DISASSOC_AP_BUSY)
[  +2.365697] wlp6s0: authenticate with <modem MAC address>
[  +0.014160] wlp6s0: send auth to <modem MAC address> (try 1/3)
[  +0.001273] wlp6s0: authenticated
[  +0.000591] wlp6s0: associate with <modem MAC address> (try 1/3)
[  +0.001359] wlp6s0: RX AssocResp from <modem MAC address> (capab=0x11 status=0 aid=8)
[  +0.000116] wlp6s0: associated
[  +0.007563] wlp6s0: Limiting TX power to 23 (23 - 0) dBm as advertised by <modem MAC address>
[Apr 1 10:29] wlp6s0: authenticate with <modem MAC address>
[  +0.013902] wlp6s0: send auth to <modem MAC address> (try 1/3)
[  +0.002488] wlp6s0: authenticated
[  +0.000568] wlp6s0: associate with <modem MAC address> (try 1/3)
[  +0.004536] wlp6s0: RX AssocResp from <modem MAC address> (capab=0x411 status=0 aid=30)
[  +0.000120] wlp6s0: associated
[  +0.023382] wlp6s0: Limiting TX power to 36 (36 - 0) dBm as advertised by <modem MAC address>
[Apr 1 10:30] wlp6s0: disassociated from <modem MAC address> (Reason: 5=DISASSOC_AP_BUSY)
[  +0.267507] wlp6s0: authenticate with <modem MAC address>
[  +0.014160] wlp6s0: send auth to <modem MAC address> (try 1/3)
[  +0.001272] wlp6s0: authenticated
[  +0.000757] wlp6s0: associate with <modem MAC address> (try 1/3)
[  +0.001420] wlp6s0: RX AssocResp from <modem MAC address> (capab=0x11 status=0 aid=24)
[  +0.000115] wlp6s0: associated
[  +0.005386] wlp6s0: Limiting TX power to 23 (23 - 0) dBm as advertised by <modem MAC address>
```

This *might* be the kind of issue that should be reported to Linux itself, but I figured it’s probably a good idea to report it here first, because I’ve never reported an issue to Linux before and don’t know how to do it properly, and it probably doesn’t hurt either way.