FS#68578 - ath problem
Attached to Project:
Arch Linux
Opened by Bob (HelpMeet) - Monday, 09 November 2020, 21:20 GMT
Last edited by Toolybird (Toolybird) - Sunday, 04 June 2023, 03:25 GMT
Opened by Bob (HelpMeet) - Monday, 09 November 2020, 21:20 GMT
Last edited by Toolybird (Toolybird) - Sunday, 04 June 2023, 03:25 GMT
|
Details
Description:
The Internet disappears (red wi-fi indicator) and the system freezes (almost always). Default kernel. The first dmesg block is when the system has been running for some time (from a minute or more), and then it stops. And the second dmesg block is when wi-fi stops working immediately during startup session. Additional info: dmesg: ath: phy0: Chip reset failed ath: phy0: Unable to reset channel, reset status -22 ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff OR ath: phy0: Mac Chip Rev 0xfffc0.f is not supported by this driver ath: phy0: Unable to initialize hardware; initialization status: -95 ath9k 0000:07:00.0: Failed to initialize device uname: Linux archlinux 5.9.6-arch1-1 #1 SMP PREEMPT Thu, 05 Nov 2020 21:00:46 +0000 x86_64 GNU/Linux |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 04 June 2023, 03:25 GMT
Reason for closing: Upstream
Additional comments about closing: Clearly an upstream problem. If still happening, please follow up with the kernel folks.
Sunday, 04 June 2023, 03:25 GMT
Reason for closing: Upstream
Additional comments about closing: Clearly an upstream problem. If still happening, please follow up with the kernel folks.
Network Controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
Edit: damn, I thought this was new. My appologies.
$ uname -r
5.9.14-arch1-1
and (TP-LINK TL-WB722N v1
$ lsusb
Bus 001 Device 005: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n
I assume, the issue is related to the driver, because other distros are affected, too:
https://github.com/ZerBea/hcxdumptool/issues/80#issuecomment-748623046
Under heavy load, the driver died.
https://bugzilla.kernel.org/show_bug.cgi?id=207397
because the arch maintainer can do nothing to solve it.