ath9k - no upper layer throughput.

Bug #404972 reported by Neil Wilson
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Ubuntu karmic Alpha-3

The ath9k wireless is very unstable on my system. If you place any load at all on the wireless the connection freezes up and upper layer packets don't appear to get through (although iw is showing a lot of RX activity, but little TX).

The association appears to remain in place - just no throughput.

Sometimes the network connection will recover after several minutes and sometimes it locks solid.

This is with the access point about six inches from the laptop and the transmission signal at 87%

ProblemType: Bug
Architecture: amd64
Date: Sun Jul 26 19:04:31 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=a1085570-586c-4eac-a7cb-52ca2f87881e
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 5536
Package: linux-image-2.6.31-3-generic 2.6.31-3.19
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-3-generic root=UUID=e544e0c3-bb61-4527-9393-26be9e351588 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
RelatedPackageVersions: linux-backports-modules-2.6.31-3-generic N/A
SourcePackage: linux
Uname: Linux 2.6.31-3-generic x86_64
dmi.bios.date: 02/27/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.03
dmi.board.name: JV50PU
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.03:bd02/27/2009:svnAcer:pnAspire5536:pvr0100:rvnAcer:rnJV50PU:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5536
dmi.product.version: 0100
dmi.sys.vendor: Acer

Revision history for this message
Neil Wilson (neil-aldur) wrote :
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Neil Wilson (neil-aldur) wrote :

re-checked this on 2.6.31-5 and the system appears to want to negotiate to MCS 32 40Mhz or MCS 33 40Mhz which causes an awful lot of drop outs and reauthentications with the AP, along with the occasional DMA hang. However it appears to be much better than before.

[ 1952.376104] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 1952.603987] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 1958.612043] wlan0: no probe response from AP 00:1c:df:a1:c7:2c - disassociating
[ 1959.797483] wlan0: authenticate with AP 00:1c:df:a1:c7:2c
[ 1959.799554] wlan0: authenticated
[ 1959.799561] wlan0: associate with AP 00:1c:df:a1:c7:2c
[ 1959.805411] wlan0: RX ReassocResp from 00:1c:df:a1:c7:2c (capab=0x431 status=0 aid=1)
[ 1959.805421] wlan0: associated

1249438707.266630: wlan0 (phy #0): scan finished
1249438713.294594: wlan0 (phy #0): deauth 00:17:c4:75:56:0c -> 00:1c:df:a1:c7:2c reason 2: Previous authentication no longer valid
1249438714.470472: wlan0 (phy #0): scan finished
1249438714.482003: wlan0 (phy #0): auth 00:1c:df:a1:c7:2c -> 00:17:c4:75:56:0c status: 0: Successful
1249438714.496868: wlan0 (phy #0): assoc 00:1c:df:a1:c7:2c -> 00:17:c4:75:56:0c status: 0: Successful
1249438827.047570: wlan0 (phy #0): scan finished

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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

Changed in linux (Ubuntu):
status: Confirmed → 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.