Bug 745362

Summary: WiFi regression in 3.1.0-0.rc9.git0.0.fc16
Product: [Fedora] Fedora Reporter: Andreas Tunek <andreas.tunek>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: gansalmon, itamar, jonathan, kernel-maint, linville, madhu.chinakonda, sgruszka
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-12 17:39:22 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 for 08
none
dmesg for 09 none

Description Andreas Tunek 2011-10-12 06:16:20 UTC 
Description of problem:
With 3.1.0-0.rc9.git0.0.fc16  I can no longer use wifi on this Acer 522. It tries to connnect to the network but it never establishes any connection. Using 3.1.0-0.rc8.git0.1.fc16 everything works fine.

Version-Release number of selected component (if applicable):
3.1.0-0.rc9.git0.0.fc16  

How reproducible:
Always



Additional info:
Smolt profile: http://www.smolts.org/client/show/pub_112b22c7-c2b3-432a-9f4a-1571a2fa8ab4
Comment 1 Stanislaw Gruszka 2011-10-12 12:49:05 UTC 
There are only two ath9k changes between rc8 and rc9 (I don't think we have something fedora specific).

commit e9f9530bb697f53dd620df290102359a3325bb23
Author: Rajkumar Manoharan <rmanohar.com>
Date:   Tue Sep 20 16:23:51 2011 +0530

    ath9k_hw: Fix Rx DMA stuck for AR9003 chips

commit ba54238552625aad2d75f455a4d3db18ea7dec68
Author: Mohammed Shafi Shajakhan <mohammed.com>
Date:   Fri Sep 23 14:33:14 2011 +0530

    ath9k: Fix a dma warning/memory leak

which could cause this breakage. First one looks more suspicious.

Andreas, are you able to rebuild -rc9 kernel with patches reverted and see if that helps. Also could you attach dmesg output.
Comment 2 Andreas Tunek 2011-10-12 17:31:25 UTC 
Created attachment 527751 [details]
dmesg for 08
Comment 3 Andreas Tunek 2011-10-12 17:37:58 UTC 
Created attachment 527752 [details]
dmesg for 09
Comment 4 Andreas Tunek 2011-10-12 17:39:22 UTC 
Seems to work now. Perhaps it was some network-manager problem?