Hello, I bisected down to commit [fcd09c90c3c5] "ath9k: use hw_random API instead of directly dumping into random.c'' while investigating a long delay when entering suspend on kernels v5.18 onward. There are other reports of hangs or unresponsiveness at https://bugs.archlinux.org/task/75138 with some more info. AFAIKT, the issue is triggered by the ath9k hwrng when the interface is up, but not associated with any AP. In this state, 'dd if=/dev/hwrng' will block for up to 231 seconds before finally returning an input/output error. Similarly, I get a kernel log message "hwrng: no data available" every 231 seconds. The hwrng will unblock when attempting to connect to an SSID that doesn't exist, but not when performing a scan, so I'm guessing AR_PHY_TST_ADC only produces new data when the phy is transmitting. Admittedly, I don't actually know if this blocking behavior is expected or not, but it certainly seems undesirable.
