Bug 772436

Summary: Wireless device fails to wakeup
Product: [Fedora] Fedora Reporter: Julian Tosh <redhat.com>
Component: kernelAssignee: John W. Linville <linville>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: extras-orphan, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, notting, shafi.wireless
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-04 15:14:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg
none
photo of crash dump none

Description Julian Tosh 2012-01-08 05:36:25 UTC 
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/
Comment 1 Julian Tosh 2012-01-08 05:38:54 UTC 
Smolt profile: http://www.smolts.org/client/show/pub_fff7264e-e0aa-4d54-9e53-92730d545133
Comment 2 Josh Boyer 2012-01-09 22:06:00 UTC 
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.
Comment 3 Julian Tosh 2012-01-22 18:41:37 UTC 
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?
Comment 4 Julian Tosh 2012-01-22 18:46:34 UTC 
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!
Comment 5 Julian Tosh 2012-01-22 18:57:23 UTC 
Created attachment 556808 [details]
photo of crash dump

this crash dump occurred during a yum update during the download phase (using wireless)
Comment 6 Mohammed Shafi 2012-01-23 04:57:13 UTC 
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
Comment 7 Dave Jones 2012-03-22 17:04:19 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 8 Dave Jones 2012-03-22 17:07:17 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 9 Dave Jones 2012-03-22 17:18:24 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 10 Josh Boyer 2012-09-04 15:14:00 UTC 
This should have been fixed in 3.3 per Mohammed's comment.