I think it’s too much uploading. If I use LibreSpeed on my own network, it crashes nearly instantly when the upload test starts, whereas if I go and use Speedtest.net, which is going to get much slower upload speeds, I can make it through probably one test before it crashes midway through the second one.
I’ve tried enabling debugging by setting ath12k.debug_mask=0xffffffff
and looking at the output, but as I mentioned and as you’ve noticed, the output from the ath12k just stops completely. Then maybe 10-30 seconds or later I start getting wmi and other timeouts from ath12k.
I thought maybe it had something to do with power management differences between Intel and AMD (since it seems to not crash on Intel machines), but turning power saving off via iw
, disabling aspm, and changing the device’s power PCIe power setting to “on” instead of “auto” does not help.
My guess now is that there’s a spinlock or something in the kernel that’s ending up in a deadlock, or that the firmware in the card is just crashing and then stops responding. I’m leaning toward the crashing part since, if I had reset the machine, the card generally won’t come back up on the first reboot. I have to reboot for a second time to get the card to start responding again.
P.S. I should also mention that I’m doing most of my testing on a BeeLink GTR7 Pro, as it exhibits the same behavior as my Framework’s and I don’t want to be tearing those open all the time for testing. Once I find something that is working on the BeeLink I’ll confirm that on one of my Framework’s before I got putting them in everything.
P.P.S. I haven’t really tested bluetooth at all; I think I at one point connected a mouse which may have worked, however I can’t recall if it was this card or another. I don’t use bluetooth audio streaming either so I wouldn’t be able to confirm that. Bluetooth for me is a secondary concern as I really don’t use it at all and is completely turned off most of the time.
Edit: Actually now that I think about it, this is the same behavior I initially had with an XPS 13 9310 several years ago that came with a Qualcomm card and used the new-at-the-time ath10k driver. I can’t recall if I just dealt with it or if it got fixed at some point as I’m usually connected to ethernet anyway. I no longer have the machine though so I can’t check it to see if it still has the same behavior or not.