168c:001c ath5k gain calibration timeout when watching flash video

Bug #580398 reported by SB
46
This bug affects 9 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

i have an Atheros wifi card (ar 5007eg) and since upgrading to lucid and the kernel that came with it (2.6.31-21, i believe), i'm experiencing some very strange wifi issues:

- at first, my wifi was very buggy and i got many "noise floor calibration timeouts" as described in many other bug reports here on launchpad. i was able to fix this and get a relatively stable wifi using the backport-modules-wireless package.

- however, i still have stability issues with the ath5k driver that can be reproduced in the following way:
1. surf the internet for hours without problems
2. start a flash video with more than just a couple of minutes (5min approx) of length
3. wifi crashes with a bunch of "gain calibration timeout" error messages
4. suspend/resume fixes the wifi connection
5. repeat

what i cant for the life of me figure out is what exactly flash videos have to do with my problem. i can surf webpages without flash videos for hours without problems, i can download hundreds of megabytes smoothly, but when i try to watch a simple flash video on youtube or on megavideo or whatever, it crashes my wifi after a relatively random amount of time. sometimes, my wifi keeps working for 10 or 20 minutes into the video, and sometimes it crashes after only 2 minutes. but in any and all cases, my wifi only crashes when i watch flash videos.

i'm filing this a new bug because a) there seems to be some connection between my wifi problems and flash, and b) i get "gain calibration timeout" errors instead of the many "noise floor calibration timeout" errors described in most other bugs (which i dont get anymore since installing the backport-modules-wireless package).

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: aplay: device_list:223: no soundcards found...
Architecture: i386
ArecordDevices: arecord: device_list:223: no soundcards found...
Date: Fri May 14 10:25:08 2010
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 064e:a101 Suyin Corp. Acer CrystalEye Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 7520
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic root=UUID=f84e7ace-ab45-40eb-b919-89cd2c0b50ea ro quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: linux
dmi.bios.date: 07/19/2007
dmi.bios.vendor: Acer
dmi.bios.version: V1.06
dmi.board.name: Fuquene
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV1.06:bd07/19/2007:svnAcer:pnAspire7520:pvrV1.06:rvnAcer:rnFuquene:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 7520
dmi.product.version: V1.06
dmi.sys.vendor: Acer
---
Architecture: i386
DistroRelease: Ubuntu 10.04
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.34-999-generic i686
UnreportableReason: The running kernel is not an Ubuntu kernel
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare saned scanner

Revision history for this message
SB (stefan-bommer) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi SB,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
SB (stefan-bommer) wrote :

i just installed the 2.6.34-999 mainline kernel, but the same thing still happens. the same gain calibration timeout error occurs.

can i help with any additional pieces of information?

tags: added: apport-collected
description: updated
tags: removed: needs-upstream-testing
Revision history for this message
SB (stefan-bommer) wrote :

actually, after using the mainline kernel for a couple of hours, i must say that my wifi is much more stable now than with the 2.6.32 kernel. i havent gotten a single gain calibration timeout error after watching 3 straight hours of flash videos. so it seems like the mainline kernel fixed the issue after all, or at least it's much more stable than the kernel i previously used.

i will report in a couple of days whether my wifi proves stable over time.

Revision history for this message
Finn10111 (finn-christiansen) wrote :

Hi,
I'm getting this error message (ath5k phy0: noise floor calibration timeout (2437MHz)) very often but I don't see any reason for this. My WiFi connection breaks down rarely (about 2 or 3 times a month), mostly it works fine. But after resuming from standy it doesn't work any more and dmesg produces the error message above.

I tried the 2.6.34 Mainline Kernel, WiFi works fine, I get no error messages and it the connection seems to be stable. Unfortunately standby doesn't work with this kernel, so I can't test my WiFi after resuming from standby.

Revision history for this message
SB (stefan-bommer) wrote :

as i said, reporting back after a couple of days: the 2.6.34 kernel seems a little stabler than the 2.6.32 kernel, but i still sometimes get gain calibration timeout erros when playing flash videos.

so i guess the error is confirmed with the mainline kernel as well.

should i post some more system logs for the 2.6.34 kernel or are the ones i already posted for the 2.6.32 kernel enough to track down the cause for the error?

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
FransSchreuder (fransschreuder1) wrote :

I am having the same problem, also AR5007EG in lucid amd64 (installing backport modules doesn't help either). Is there any information that I can add to this bug report?

Revision history for this message
Alexander Fougner (fougner) wrote :

I, too, have this problem.

Wall of text from dmesg:

[ 516.821612] ath5k phy0: gain calibration timeout (2412MHz)
[ 517.406490] ath5k phy0: gain calibration timeout (2442MHz)
[ 517.991777] ath5k phy0: gain calibration timeout (2472MHz)
[ 518.578231] ath5k phy0: gain calibration timeout (2417MHz)
[ 519.163844] ath5k phy0: gain calibration timeout (2447MHz)

repeat 21043500 times.

I'm on Linux 2.6.35-02063504-generic #201008271919 SMP Fri Aug 27 19:22:15 UTC 2010 x86_64 GNU/Linux

I have a AR5007EG too I think.

Revision history for this message
Kfost (kfost) wrote :

For me the wireless timeout happens on every other boot up . I have to shut down (not reboot) and the system comes up fine. My current fix is to power up, shut down and then power up again. It always works on the second boot and never works on the first. Almost like something fails to get initialized after wireless is working and requires two cycles of rebooting before getting re-initialized. I've had this problem since the Lucid upgrade. And the installation of backport-modules does not resolve the problem.

Revision history for this message
FransSchreuder (fransschreuder1) wrote :

According to
https://bugzilla.kernel.org/show_bug.cgi?id=16436
someone found out that this bug is related with powernow-k8. This is a statically linked part of the kernel, but can also be linked as a module. Would it be possible for the Ubuntu maintainers to build the default kernel with powernow-k8 as a module, so that the many people with an atheros card suffering with this problem could easily blacklist the module?

Revision history for this message
Crusoe (daniel-a-joyce) wrote :

This archlinux post suggests powernow-k8 is responsible as well

https://bugs.archlinux.org/task/18982

 Comment by Mauro Santos (R00KIE) - Monday, 12 April 2010, 11:33 GMT-5
I have found a workaround until this gets sorted in the kernel.

I have an AMD cpu in my notebook and I have found that if I use phc-k8 [1] instead of powernow-k8 then
wireless works fine and I still have cpu frequency scaling. If anyone has an INTEL cpu and is also affected,
phc-intel [2] might be worth a try (if the problem is connected with modprobing the cpu driver).

Can we get a kernel with powernow-k8 available a module?

I upgraded to 2.6.35, and while the problem occurs less frequently, it still occurs.

Kernel with phc-k8 for ubuntu 10.10:

http://david.gnedt.eu/blog/2010/10/10/linux-phc-for-ubuntu-10-10-maverick-meerkat/

tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

SB, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

tags: added: regression-release
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Lex Ross (lross) wrote :

I don't think it is Flash related issue. I have the same problem on x64 11.10 and 12.04 up to the recent kernel 3.2.0-29
In my case, the bug causes intermittent and weak signal to be received even in the close proximity of an access point, and slow wireless connection. Then in about an hour or so the wireless connection is broken and there is no way to reconnect to the access point until reboot. I get the following error messages from ath5k:

Aug 16 22:43:28 mars kernel: [210282.485123] ath5k phy0: gain calibration timeout (2427MHz)
Aug 16 22:43:28 mars kernel: [210282.939973] ath5k phy0: gain calibration timeout (2432MHz)
Aug 16 22:43:29 mars kernel: [210283.393702] ath5k phy0: gain calibration timeout (2437MHz)
Aug 16 22:43:29 mars kernel: [210283.845470] ath5k phy0: gain calibration timeout (2442MHz)
Aug 16 22:43:30 mars kernel: [210284.297389] ath5k phy0: gain calibration timeout (2447MHz)
Aug 16 22:43:30 mars kernel: [210284.749028] ath5k phy0: gain calibration timeout (2452MHz)
Aug 16 22:43:31 mars kernel: [210285.199180] ath5k phy0: gain calibration timeout (2457MHz)
Aug 16 22:43:31 mars kernel: [210285.648754] ath5k phy0: gain calibration timeout (2462MHz)
Aug 16 22:43:33 mars kernel: [210287.454040] net_ratelimit: 3 callbacks suppressed
Aug 16 22:43:33 mars kernel: [210287.454045] ath5k phy0: gain calibration timeout (2412MHz)

Revision history for this message
Lex Ross (lross) wrote :

Actually, I have to power off my laptop to get the wireless working again. Can anyone please confirm that any of the following patches get into Ubuntu kernel:

http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=62e2c102cc1d2600381410c089ca9a37359577d2
http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=5c17ddc4a047c59638c7eb8537aa887a1ddb9b0b

Thanks.

Revision history for this message
penalvch (penalvch) wrote :

Lex Ross, please do not solicit people to verify kernel patches.

If you are having a problem in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette

When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

summary: - ath5k gain calibration timeout when watching flash video
+ 168c:001c ath5k gain calibration timeout when watching flash video
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.