Hide Forgot
Description of problem: Wireless works fine for the first few minutes after boot. After a period of time, wireless connectivity breaks. Version-Release number of selected component (if applicable): How reproducible: Intermittent Steps to Reproduce: 1.Boot and login 2.Establish wireless connection 3.Leave idle (establishing a constant ping seems to keep it alive much longer) Actual results: Wireless will lose connection to AP Expected results: Wireless maintain constant connection Additional info: ath: Failed to wakeup in 500us ath: Failed to stop TX DMA, queues=0x10f! ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff ath: Could not stop RX, we could be confusing the DMA engine when we start RX up ath: Chip reset failed ath: Unable to reset channel, reset status -22 ath: Failed to stop TX DMA, queues=0x10f! ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff ath: Could not stop RX, we could be confusing the DMA engine when we start RX up dmesg entries for ath device: http://fpaste.org/93aY/ Network device from lspci: http://fpaste.org/ki7O/
Smolt profile: http://www.smolts.org/client/show/pub_fff7264e-e0aa-4d54-9e53-92730d545133
Created attachment 551683 [details] dmesg Attaching the dmesg. The fpaste is already expired. In the future, please avoid using fpaste/pastebin style things for bug reports.
I'm going to have to return this Laptop to the store soon if no progress is made. Is there any additional debug information I can supply to help the developers?
Also, might there be a workaround to reset this chip? Something less than rebooting the laptop? If I can create a shortcut to click when this problem arises, it may be acceptable to keep the laptop until a solid fix is made. Thanks!
Created attachment 556808 [details] photo of crash dump this crash dump occurred during a yum update during the download phase (using wireless)
crash should be addressed by http://comments.gmane.org/gmane.linux.kernel.wireless.general/83710 let me check out the other issue can be quickly verified by http://linuxwireless.org/en/users/Download#Where_to_download_bleeding_edge
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
This should have been fixed in 3.3 per Mohammed's comment.