Arch Linux

williamkray

Member

Registered: 2010-11-06

Posts: 64

Wireless Connection drops randomly, kernel related...

Since one of the many kernel updates in the past week, i'm noticing my wireless connection just... stops. I can't do anything to bring it back up except reboot. which gets very annoying.

the following was pulled from journalctl:

Jun 09 11:56:22 sputnik systemd[1]: Starting Bluetooth.
Jun 09 11:56:22 sputnik systemd[1]: Reached target Bluetooth.
Jun 09 11:56:23 sputnik kernel: wlan0: authenticate with 10:6f:3f:0c:10:96
Jun 09 11:56:23 sputnik kernel: wlan0: send auth to 10:6f:3f:0c:10:96 (try 1/3)
Jun 09 11:56:23 sputnik kernel: wlan0: authenticated
Jun 09 11:56:23 sputnik kernel: wlan0: associate with 10:6f:3f:0c:10:96 (try 1/3)
Jun 09 11:56:23 sputnik kernel: wlan0: RX AssocResp from 10:6f:3f:0c:10:96 (capab=0x411 status=0 aid=4)
Jun 09 11:56:23 sputnik kernel: wlan0: associated
Jun 09 11:58:47 sputnik kernel: ath: phy0: Failed to wakeup in 500us
Jun 09 11:58:47 sputnik kernel: ath: phy0: Failed to wakeup in 500us
Jun 09 11:58:47 sputnik kernel: ath: phy0: Failed to wakeup in 500us
Jun 09 11:58:47 sputnik kernel: ath: phy0: Failed to wakeup in 500us
Jun 09 11:58:47 sputnik kernel: ath: phy0: Failed to stop TX DMA, queues=0x10f!
Jun 09 11:58:47 sputnik kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jun 09 11:58:47 sputnik kernel: ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jun 09 11:58:47 sputnik kernel: ath: phy0: Chip reset failed
Jun 09 11:58:47 sputnik kernel: ath: phy0: Unable to reset channel, reset status -22
Jun 09 11:58:47 sputnik kernel: ath: phy0: Failed to stop TX DMA, queues=0x10f!

and it just repeats. i'm still experimenting to see what might fix this, but does anybody have any leads?

kernel: 3.9.4-1-ARCH
Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)

tips, tricks, and any other general input is greatly welcome. my next step is to disable power management of the networking card and see if it's a workaround... otherwise just wait for the next kernel and see if it's fixed