Bug 814889

Summary: Wireless connection speed drops to zero for about a minute; kernel log flooded
Product: [Fedora] Fedora Reporter: calcdude84se
Component: kernelAssignee: John W. Linville <linville>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda, shafi.wireless
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: 2012-11-14 15:29:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The contents of /bin/dmesg for one of these 1-minute downtimes
none
Results of lspci -vvvxxx none

Description calcdude84se 2012-04-21 02:41:36 UTC
Created attachment 579133 [details]
The contents of /bin/dmesg for one of these 1-minute downtimes

Description of problem:
Every so often (it seems like once every 10 minutes or so) my upload and download rates will drop to zero for about a minute. Checking /bin/dmesg, it's flooded with various messages, repeated several times (see attached)

Version-Release number of selected component (if applicable):
Kernel version 3.3.2-1.fc16.x86_64

How reproducible:
Connect to a WiFi network and eventually experience a sudden lack of connection for about a minute.

Expected results:
No sudden loss of connection.

Additional info:
ath9k driver

Comment 1 John W. Linville 2012-04-23 14:41:12 UTC
It looks like your link is going up and down rather quickly.  Is it possible that you are near some source of intermittent interference (like a public microwave oven in a breakroom)?

Comment 2 Mohammed Shafi 2012-04-23 16:16:27 UTC
please answer John's queries and provide us with as many debug data, lspci -vvvxxx

http://linuxwireless.org/en/users/Drivers/ath9k/debug

Comment 3 calcdude84se 2012-04-23 21:11:19 UTC
Created attachment 579695 [details]
Results of lspci -vvvxxx

Comment 4 calcdude84se 2012-04-23 21:23:31 UTC
> It looks like your link is going up and down rather quickly.  Is it possible
> that you are near some source of intermittent interference (like a public
> microwave oven in a breakroom)?
This is at home, and there are no non-wifi radio devices I am aware of besides a microwave which is definitely not in use when this happens. If this is radio interference, I have no idea what's causing it.

> please answer John's queries and provide us with as many debug data, lspci
> -vvvxxx
Results of lspci -vvvxxx attached. I will attempt to install the modified kernel at a later point.

Also, I have a Windows computer that doesn't seem to have this problem. Could it possibly be hardware-created interference? If that's a reasonable possibility, how would I tell?

Comment 5 Dave Jones 2012-10-23 15:35:17 UTC
# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 6 Justin M. Forbes 2012-11-14 15:29:49 UTC
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.