168c:0032 [Asus G75VX] Slow wireless with AR9485 ath9k

[Boris]

With the latest raring kernel image (linux-signed-image-3.8.0-18-generic) my wireless connection becomes very slow after a few minutes (ping to my AP increases from < 1ms to ~ 900ms).
Kernel 3.8.0.17.27 is still fine, other wireless devices continue to work fine if the problem occurs.
HW is AR9485 (ath9k) 1x1 802.11n in Asus G75VX laptop, AP is Asus RT-AC66U.
~
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 13.04
EcryptfsInUse: Yes
HibernationDevice:
 #RESUME=UUID=8c98d3e1-50af-4c74-820b-e3f29cefc50c
 #RESUME=/dev/mapper/cryptswap1
InstallationDate: Installed on 2013-03-27 (17 days ago)
InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2)
MachineType: ASUSTeK COMPUTER INC. G75VX
MarkForUpload: True
NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed root=UUID=93525b3d-45ae-49d5-be79-e00da8ca123b ro bootchart=disable
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-17-generic N/A
 linux-backports-modules-3.8.0-17-generic N/A
 linux-firmware 1.105
Tags: raring
Uname: Linux 3.8.0-17-generic x86_64
UpgradeStatus: Upgraded to raring on 2013-04-06 (8 days ago)
UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape vboxusers video
dmi.bios.date: 02/27/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G75VX.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G75VX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VX.206:bd02/27/2013:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G75VX
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[gfmichaud (gfmichaud-linux-kernel-bugs)]

Wifi connection with an Atheros AR9485 card is very unstable (bad quality, and very bad range).
At the beginning connection quality stays where it reasonably should be, but after few seconds it drops to poor values :

:~$ sudo iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11bgn ESSID:"Pluff"
          Mode:Managed Frequency:2.412 GHz Access Point: 94:0C:6D:C5:8B:B4
          Bit Rate=54 Mb/s Tx-Power=15 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=46/70 Signal level=-64 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:4 Missed beacon:0
......
:~$ sudo iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11bgn ESSID:"Pluff"
          Mode:Managed Frequency:2.412 GHz Access Point: 94:0C:6D:C5:8B:B4
          Retry long limit:7 RTS thr:off Fragment thr:off
          Encryption key:off
          Power Management:off
          Bit Rate=54 Mb/s Tx-Power=15 dBm
          Link Quality=28/70 Signal level=-82 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:4 Missed beacon:0

--- --- --- --- --- --- --- --- ---

This was tested on (cat /proc/version) :
- Linux version 3.5.0-17-generic (buildd@allspice) (gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) ) #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012
which is the standard Ubuntu 12.10 kernel and
- Linux version 3.7.0-999-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201210210405 SMP Sun Oct 21 08:05:46 UTC 2012
which is the latest upstream kernel

The exact name of the network card is (lspci) :
02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)

--- --- --- --- --- --- --- --- ---

This bug is related to Ubuntu Launchpad bug n°971809.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971809

[emailadhoc (emailadhoc-linux-kernel-bugs)]

I have an Atheros Communications Inc. AR9485 (revision 1) and I'm experiencing the same problems under kernel 3.6.7 (fedora 18).

The speed is very low when I walk some meters away from the access point, any network around me appears to have a very low signal level. Sometimes, even if the bit rate is set at 1mbps, the connection just drops and I can't re-associate since the network appears to be out-of-range. I usually have to restart the adapter. I initially thought that someone was jamming me, since I use a 14dbi directional antenna (and my ap is set at 23-26 dBm)

[gfmichaud (gfmichaud-linux-kernel-bugs)]

The problem is still here in 3.7 final.

[sujith (sujith-linux-kernel-bugs)]

A few patches updating AR9485 support have been posted. Once compat-drivers is updated to the latest linux-next snapshot, they can be used.

Regarding the signal issue, I can reproduce it. It drops as soon as ANI kicks in, right after this message:

ath: phy5: Starting IQ Cal and Correction for Chain 0
ath: phy5: Original: Chn 0 iq_corr_meas = 0x002ba228
ath: phy5: Chn 0 pwr_meas_i = 0x07e86ffe
ath: phy5: Chn 0 pwr_meas_q = 0x079f1692
ath: phy5: iqCorrNeg is 0x00000000
ath: phy5: Chn 0 iCoff = 0x00000005
ath: phy5: Chn 0 qCoff = 0x00000002
ath: phy5: Chn 0 : iCoff = 0x7b qCoff = 0x2
ath: phy5: Register offset (0x98dc) before update = 0x20000000
ath: phy5: Register offset (0x98dc) QI COFF (bitfields 0x00003f80) after update = 0x20003d82
ath: phy5: Register offset (0x98dc) QQ COFF (bitfields 0x0000007f) after update = 0x20003d82
ath: phy5: IQ Cal and Correction done for Chain 0
ath: phy5: IQ Cal and Correction (offset 0x98dc) enabled (bit position 0x00004000). New Value 0x20007d82

I'll take a look at this issue.

[gfmichaud (gfmichaud-linux-kernel-bugs)]

@Sujith

I don't know what ANI is, but I saw there
https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX31E
that
- fixing the wireless connection's BSSID
- disabling the ath9k driver ani feature with "echo 1 > /sys/kernel/debug/ieee80211/phy0/ath9k/disable_ani"
could help, but it did not really solved the problem for me.

Maybe it helps ?

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1168819

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[Joseph Salisbury (jsalisbury)]

Does this issue go away if you boot back into the 3.8.0-17 kernel?

[Boris (boris-woerner)]

On 15/04/13 18:01, Joseph Salisbury wrote:
> Does this issue go away if you boot back into the 3.8.0-17 kernel?
>
> ** Changed in: linux-signed (Ubuntu)
> Importance: Undecided => Medium
Yes, 3.8.0-17 is definitely fine (using it right now as workaround).

[Boris (boris-woerner)]

This seems to be fixed with 3.8.0-19, since installing that the wireless is fine again.

[Boris (boris-woerner)]

Not fixed, the problem just reappeared with 3.8.0-19 this morning:
PING asus (10.85.3.65) 56(84) bytes of data.
64 bytes from asus (10.85.3.65): icmp_req=1 ttl=64 time=945 ms
64 bytes from asus (10.85.3.65): icmp_req=2 ttl=64 time=946 ms
64 bytes from asus (10.85.3.65): icmp_req=3 ttl=64 time=900 ms
Asus is my router, normal ping times are ~1ms.

I'll try to run the apport again with the current kernel, the original run was I think with 3.8.0-17 and might not show the actual problem.

[Boris (boris-woerner)]

apport information

[Boris (boris-woerner)]

apport information

[tomwys (tomwys-linux-kernel-bugs)]

Related:
https://bugzilla.kernel.org/show_bug.cgi?id=55901
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1160188

I have same issue on Asus S500CA.

02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)

Linux tomwys-laptop 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[Chris (chrisjlee)]

Having this issue on asus vivobook c500 as well. Found a thread recently on ubuntu forums with others confirming this:
http://ubuntuforums.org/showthread.php?t=2141461

[gfmichaud (gfmichaud-linux-kernel-bugs)]

Still here in 3.10.0-031000rc2-generic.

[gfmichaud (gfmichaud-linux-kernel-bugs)]

(In reply to comment #6)
> Still here in 3.10.0-031000rc2-generic.

If I move away (~5m) from the hotspot, the connection works perfectly fine for a while ; then it suddenly & inexplicably drops down, and never comes back.

If I move again closer to the hotspot, /var/log shows what is written in CLOSER.txt.

If I move again farther, after a random amount of time I am disconnected and /var/log shows what is written in FARTHER.txt.

I insist on saying that until this sudden disconnection, the connection works perfectly fine (good bandwith & no lag).
This is a Linux-related problem since in the same location everything works perfectly fine with Windows 7.

[sujith (sujith-linux-kernel-bugs)]

The second patch is applicable for a specific model of AR9485. Can you please attach the output of "dmidecode" to this bug ? Also, the contents of "modal_eeprom" in the ath9k debugfs directory.

The power management issue appears to be different, so we can analyze it in a new bug report.

[sujith (sujith-linux-kernel-bugs)]

(In reply to comment #99)
> OK ! If you need me test anything, feel free to ask.

Please test this patch: https://patchwork.kernel.org/patch/2696121/

[jkp (jkp-linux-kernel-bugs)]

Here's the info from kernel version 3.8.0 (suppose that doesn't matter but just saying in case), (that's because for some reason the internal display of this computer doesn't work with the 3.10rc4 kernel and I'm on the move without a display cable).

modal_eeprom:

   2GHz modal Header :
 Chain0 Ant. Control : 16
 Chain1 Ant. Control : 16
 Chain2 Ant. Control : 16
 Ant. Common Control : 1088
Ant. Common Control2 : 559240
           Ant. Gain : 0
       Switch Settle : 44
    Chain0 xatten1DB : 30
    Chain1 xatten1DB : 0
    Chain2 xatten1DB : 0
Chain0 xatten1Margin : 5
Chain1 xatten1Margin : 0
Chain2 xatten1Margin : 0
          Temp Slope : 38
          Volt Slope : 0
      spur Channels0 : 180
      spur Channels1 : 140
      spur Channels2 : 164
      spur Channels3 : 100
      spur Channels4 : 0
 Chain0 NF Threshold : -1
 Chain1 NF Threshold : 0
 Chain2 NF Threshold : 0
          Quick Drop : 0
       txEndToXpaOff : 0
      xPA Bias Level : 0
  txFrameToDataStart : 14
       txFrameToPaOn : 14
      txFrameToXpaOn : 14
              txClip : 3
    ADC Desired size : -30
   5GHz modal Header :
 Chain0 Ant. Control : 0
 Chain1 Ant. Control : 0
 Chain2 Ant. Control : 0
 Ant. Common Control : 272
Ant. Common Control2 : 139810
           Ant. Gain : 0
       Switch Settle : 45
    Chain0 xatten1DB : 0
    Chain1 xatten1DB : 0
    Chain2 xatten1DB : 0
Chain0 xatten1Margin : 0
Chain1 xatten1Margin : 0
Chain2 xatten1Margin : 0
          Temp Slope : 68
          Volt Slope : 0
      spur Channels0 : 0
      spur Channels1 : 0
      spur Channels2 : 0
      spur Channels3 : 0
      spur Channels4 : 0
 Chain0 NF Threshold : -1
 Chain1 NF Threshold : 0
 Chain2 NF Threshold : 0
          Quick Drop : 0
       txEndToXpaOff : 0
      xPA Bias Level : 0
  txFrameToDataStart : 14
       txFrameToPaOn : 14
      txFrameToXpaOn : 14
              txClip : 3
    ADC Desired size : -30

dmidecode with some id info removed:

# dmidecode 2.11
# SMBIOS entry point at 0xda152198
SMBIOS 2.7 present.
23 structures occupying 1673 bytes.
Table at 0xDA130018.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
 Vendor: American Megatrends Inc.
 Version: TX300CA.207
 Release Date: 01/03/2013
 Address: 0xF0000
 Runtime Size: 64 kB
 ROM Size: 6144 kB
 Characteristics:
  PCI is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  BIOS ROM is socketed
  EDD is supported
  5.25"/1.2 MB floppy services are supported (int 13h)
  3.5"/720 kB floppy services are supported (int 13h)
  3.5"/2.88 MB floppy services are supported (int 13h)
  Print screen service is supported (int 5h)
  8042 keyboard serv...

[sujith (sujith-linux-kernel-bugs)]

(In reply to comment #110)
> Here's the info from kernel version 3.8.0 (suppose that doesn't matter but
> just
> saying in case), (that's because for some reason the internal display of this
> computer doesn't work with the 3.10rc4 kernel and I'm on the move without a
> display cable).

Thanks.

Here is a patch adding support for this card:
http://msujith.org/patches/wl/Jun-13-2013/0001-ath9k-Add-custom-parameters-for-CUS198.patch

Can you test this ? This will apply on top of the earlier patch ("Assign default xlna config for AR9485").

Also, after you explicitly unload/reload ath9k (modprobe -r ath9k; modprobe ath9k), the line "Set parameters for CUS198" should be seen in dmesg.

[jkp (jkp-linux-kernel-bugs)]

Applied first https://patchwork.kernel.org/patch/2696121/ then http://msujith.org/patches/wl/Jun-13-2013/0001-ath9k-Add-custom-parameters-for-CUS198.patch on top of Ubuntu kernel 3.8.0-26 which I have running now.

Patch(1) applied it with some fuzz and I had to manually apply the patch to pci.c.

Seems to work fine with a short test: decent bandwidth, keeps up, shows 65 Mbps as rate, link quality between 40 and 50, and I get the kernel message:

ath: phy1: Set parameters for CUS198

I can test later with some other kernel versions if needed.

[gfmichaud (gfmichaud-linux-kernel-bugs)]

(In reply to comment #109)
> (In reply to comment #99)
> > OK ! If you need me test anything, feel free to ask.
>
> Please test this patch: https://patchwork.kernel.org/patch/2696121/

I need a few precisions :
- do I have to apply this patch only ?
- on top of the 3.10-rc5 kernel ?
- with powersave mode off ?
- what do I have to post (logs...) after testing ?

[sujith (sujith-linux-kernel-bugs)]

On top of Linus Torvalds' tree, apply these patches:

https://patchwork.kernel.org/patch/2696121/
http://msujith.org/patches/wl/Jun-13-2013/0001-ath9k-Add-custom-parameters-for-CUS198.patch

PS has been disabled by default in mainline now.

Reload ath9k and in dmesg, the message "Set parameters for CUS198" should be seen.

[gfmichaud (gfmichaud-linux-kernel-bugs)]

Sorry I'm a kernel newbie...
How can I download Linus' tree ?
Previously, I downloaded the sources from kernel.org

[sujith (sujith-linux-kernel-bugs)]

Hm, in that case, you can just apply the patches on top of the 3.10-rc5 tarball.

[jkp (jkp-linux-kernel-bugs)]

Tested also with mainline 3.9.5, applied first https://patchwork.kernel.org/patch/2696121/ then http://msujith.org/patches/wl/Jun-13-2013/0001-ath9k-Add-custom-parameters-for-CUS198.patch. Applied with some fuzz, no manual intervention required, results look the same as with 3.8.0.

[jkp (jkp-linux-kernel-bugs)]

Same good results with mainline 3.10-rc5, applied first
https://patchwork.kernel.org/patch/2696121/ then
http://msujith.org/patches/wl/Jun-13-2013/0001-ath9k-Add-custom-parameters-for-CUS198.patch.
Applied with some fuzz, no manual intervention required, results look the same
as with 3.8.0 and 3.9.5.

[jkp (jkp-linux-kernel-bugs)]

Out of topic probably, but as I see that bluetooth is in the same device: seems like there is a problem with bluetooth also, but could be something else than the driver. Device is found, hciconfig shows bytes sent and received, but hcitool scan doesn't show devices.

[sujith (sujith-linux-kernel-bugs)]

What does lsusb -v show ?

[jkp (jkp-linux-kernel-bugs)]

Bus 001 Device 003: ID 13d3:3402 IMC Networks
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize0 64
  idVendor 0x13d3 IMC Networks
  idProduct 0x3402
  bcdDevice 0.01
  iManufacturer 1
  iProduct 2
  iSerial 3
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 177
    bNumInterfaces 2
    bConfigurationValue 1
    iConfiguration 4
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 224 Wireless
      bInterfaceSubClass 1 Radio Frequency
      bInterfaceProtocol 1 Bluetooth
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 224 Wireless
      bInterfaceSubClass 1 Radio Frequency
      bInterfaceProtocol 1 Bluetooth
      iInterface 0
      Endpoint Descriptor:
       bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x03 EP 3 OUT
        bmAttributes 1
    ...

[sujith (sujith-linux-kernel-bugs)]

Hm, that's weird. What does 'ls -l /sys/bus/usb/drivers' show ? Does it have ath3k ?

[jkp (jkp-linux-kernel-bugs)]

No - there's "btusb" with contents:

lrwxrwxrwx 1 root root 0 kesä 13 19:30 1-1.1:1.0 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0
lrwxrwxrwx 1 root root 0 kesä 13 19:30 1-1.1:1.1 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1
--w------- 1 root root 4096 kesä 13 19:30 bind
lrwxrwxrwx 1 root root 0 kesä 13 19:30 module -> ../../../../module/btusb
-rw-r--r-- 1 root root 4096 kesä 13 19:30 new_id
-rw-r--r-- 1 root root 4096 kesä 13 19:30 remove_id
--w------- 1 root root 4096 kesä 13 19:02 uevent
--w------- 1 root root 4096 kesä 13 19:30 unbind

[gfmichaud (gfmichaud-linux-kernel-bugs)]

One last question before testing : do I have to disable ATH9K_RATE_CONTROL or not ?

[jkp (jkp-linux-kernel-bugs)]

Hmm, probably ran lsusb -v without root access, here's with root, has some more info:

Bus 001 Device 003: ID 13d3:3402 IMC Networks
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize0 64
  idVendor 0x13d3 IMC Networks
  idProduct 0x3402
  bcdDevice 0.01
  iManufacturer 1 Atheros Communications
  iProduct 2 Bluetooth USB Host Controller
  iSerial 3 Alaska Day 2006
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 177
    bNumInterfaces 2
    bConfigurationValue 1
    iConfiguration 4 BT HCI
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 224 Wireless
      bInterfaceSubClass 1 Radio Frequency
      bInterfaceProtocol 1 Bluetooth
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 224 Wireless
      bInterfaceSubClass 1 Radio Frequency
      bInterfaceProtocol 1 Bluetooth
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0000 1x 0 bytes
        bInterval 1
      Endpoint De...

[sujith (sujith-linux-kernel-bugs)]

(In reply to comment #124)
> One last question before testing : do I have to disable ATH9K_RATE_CONTROL or
> not ?

Yes, ATH9K_RATE_CONTROL has to be disabled.

[sujith (sujith-linux-kernel-bugs)]

(In reply to comment #125)
> Hmm, probably ran lsusb -v without root access, here's with root, has some
> more
> info:
>
> Bus 001 Device 003: ID 13d3:3402 IMC Networks
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 1.10
> bDeviceClass 224 Wireless
> bDeviceSubClass 1 Radio Frequency
> bDeviceProtocol 1 Bluetooth
> bMaxPacketSize0 64
> idVendor 0x13d3 IMC Networks
> idProduct 0x3402
> bcdDevice 0.01
> iManufacturer 1 Atheros Communications
> iProduct 2 Bluetooth USB Host Controller
> iSerial 3 Alaska Day 2006

Ok, I am not familiar with bluetooth - I'll try to get more information.

[jkp (jkp-linux-kernel-bugs)]

Ah, I wondered I might have forgotten something with my 3.8.0 test - now I remember, it was ATH9K_RATE_CONTROL:

# grep RATE_CONTROL .config
CONFIG_ATH9K_RATE_CONTROL=y

Seems to work quite well even with this.

For 3.9.5 and 3.10 I had it disabled:

# grep RATE_CONTROL .config
# CONFIG_ATH9K_RATE_CONTROL is not set

[gfmichaud (gfmichaud-linux-kernel-bugs)]

So I've applied both patches on top of the 3.10-rc5 kernel.

Everything looks OK :
gfmichaud@dragonfly:~$ sudo rmmod ath9k
[sudo] password for gfmichaud:
gfmichaud@dragonfly:~$ sudo modprobe ath9k
gfmichaud@dragonfly:~$ dmesg | grep -i parameters
[ 289.311397] ath: phy0: ANI parameters: SI=3, ofdmWS=on FS=7 MRCcck=on listenTime=25 ofdmErrs=64 cckErrs=892
[ 297.359862] ath: phy1: Set parameters for CUS198

However, it looks like powersave is on by default (I've removed the item in /etc/pm/power.d that disabled it) :
gfmichaud@dragonfly:~$ iw dev wlan0 get power_save
Power save: on

Link quality seems to have improved a lot :
- in 3.8 without patches, "iw dev wlan0 link" shows me "signal" between -74 and -86 dBm
- in 3.10-rc5 with the patches, it shows me "signal" between -55 and -62 dBm

I'll do futher testing and report here.

[sujith (sujith-linux-kernel-bugs)]

(In reply to comment #129)
> However, it looks like powersave is on by default (I've removed the item in
> /etc/pm/power.d that disabled it) :
> gfmichaud@dragonfly:~$ iw dev wlan0 get power_save
> Power save: on

The PS/rate-control patches will be in -rc6.

[gfmichaud (gfmichaud-linux-kernel-bugs)]

I've been using it with all doors closed at home and experienced no disconnection and no lag.
Looks really great !!! :-)

[jkp (jkp-linux-kernel-bugs)]

No problems here either, seems to work fine in longer term (well, a few hours) use too. Power management has been on for me though so far, will try with power management off.

[jkp (jkp-linux-kernel-bugs)]

With power management off, when I look at the iwconfig bit rate every five seconds, it's mostly 65 Mbps but about every once in 25 .. once in 50 it's 1 Mbps.

[jkp (jkp-linux-kernel-bugs)]

With power management off, occasionally there are longer periods of low speed (1..30 Mbps) and this affects also practical usability quite a lot.

[sujith (sujith-linux-kernel-bugs)]

Can you open separate bugs for the PS and bluetooth issues ? Thanks.

John, I think this bug can be closed now, patch has been sent:
https://patchwork.kernel.org/patch/2718041/

[jkp (jkp-linux-kernel-bugs)]

OK, I will - and big thanks for making the wireless much more usable!

[gfmichaud (gfmichaud-linux-kernel-bugs)]

Yes, thank you very very much ! :-)

[jkp (jkp-linux-kernel-bugs)]

Bugs 59691 & 59701 are the power management and bluetooth bugs:

https://bugzilla.kernel.org/show_bug.cgi?id=59691

https://bugzilla.kernel.org/show_bug.cgi?id=59701

[gfmichaud (gfmichaud-linux-kernel-bugs)]

How do we know in which kernel the patches will be committed ?
Will the be in 3.10 or later ?

[linville (linville-linux-kernel-bugs)]

Presumably in 3.11...

[Nikolaj Sheller (nikolajsheller)]

Bug #947697 seems related.

This problem affects me on 13.04.
uname: Linux HTPC2 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Stable connection with good ping times, but throughput is measured in 10-20 kB/s.
Other linux machines on the same access point (NETGEAR WNDR3700v2) get 0.5 to 1 mB/s.

[Nikolaj Sheller (nikolajsheller)]

Additionaly I noticed that attempting a data transfer over wifi on the effected machine has a detrimantal effect on ping times for other machines on the same access point.

[penalvch (penalvch)]

Boris, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[artur.szymczak (artur.szymczak-linux-kernel-bugs)]

Was it merged in 3.11-rc3?

[harroxelas (harroxelas-linux-kernel-bugs)]

Were the patches merged on 3.11-rc6?

[sujith (sujith-linux-kernel-bugs)]

The fixes are in the 3.11 release.

[linville (linville-linux-kernel-bugs)]

*** Bug 55171 has been marked as a duplicate of this bug. ***

[linville (linville-linux-kernel-bugs)]

*** Bug 55901 has been marked as a duplicate of this bug. ***

[penalvch (penalvch)]

Pending results of https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1168819/comments/29 .

[eugene.shatokhin (eugene.shatokhin-linux-kernel-bugs)]

(In reply to Sujith from comment #143)
> The fixes are in the 3.11 release.

Thanks! Could you queue them for the stable kernel trees as well?

[Boris (boris-woerner)]

Sorry I noticed this was still open - problem did disappear after a few months with newer kernel version

[penalvch (penalvch)]

Boris, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1168819/comments/31 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[jesuinovieira_ (jesuinovieira-linux-kernel-bugs)]

Hi, can anyone help me?

How do I apply a patch? I got the same problem.