Bug 15313 - Lot of packet loss using ath9k and network-manager
Summary: Lot of packet loss using ath9k and network-manager
Status: CLOSED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-15 09:00 UTC by Franck Routier
Modified: 2010-11-23 18:34 UTC (History)
11 users (show)

See Also:
Kernel Version: 2.6.33-rc7
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Franck Routier 2010-02-15 09:00:18 UTC
My wifi connection is hardly usable using 2.6.33-999 201002121003 with atheros AR9285 chipset and ath9k driver.

Pinging the router shows ~40% packet loss :

 ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=1.62 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=1.67 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=1.40 ms
64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=4.72 ms
64 bytes from 10.0.0.1: icmp_seq=7 ttl=64 time=1.79 ms
64 bytes from 10.0.0.1: icmp_seq=8 ttl=64 time=2.87 ms
64 bytes from 10.0.0.1: icmp_seq=9 ttl=64 time=3.16 ms
64 bytes from 10.0.0.1: icmp_seq=10 ttl=64 time=1.42 ms
64 bytes from 10.0.0.1: icmp_seq=13 ttl=64 time=1.44 ms
64 bytes from 10.0.0.1: icmp_seq=14 ttl=64 time=1.68 ms
64 bytes from 10.0.0.1: icmp_seq=17 ttl=64 time=1.68 ms
64 bytes from 10.0.0.1: icmp_seq=20 ttl=64 time=1.42 ms
64 bytes from 10.0.0.1: icmp_seq=23 ttl=64 time=1.99 ms
64 bytes from 10.0.0.1: icmp_seq=26 ttl=64 time=1.38 ms
^C
--- 10.0.0.1 ping statistics ---
26 packets transmitted, 14 received, 46% packet loss, time 25058ms
rtt min/avg/max/mdev = 1.389/2.022/4.722/0.915 ms

I am using network-manager to handle the configuration process.

This happens on a WPA connection as well as on a plain connection (no security) connection.

iwconfig shows :

wlan0     IEEE 802.11bgn  ESSID:"axege*net_sts"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:13:10:1F:5B:F0   
          Bit Rate=54 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=62/70  Signal level=-48 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lspci -vvv shows :

02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
	Subsystem: Foxconn International, Inc. Device e017
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at e7a00000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: ath9k
	Kernel modules: ath9k
Comment 1 John W. Linville 2010-02-15 14:14:01 UTC
OK, I'll bite -- what is 2.6.33-999?
Comment 2 Franck Routier 2010-02-15 16:25:12 UTC
Sorry. It is actually 2.6.33-rc7.

(2.6.33-999 is the name given to the 'latest' 2.6.33 mainline kernel in Ubuntu MainlineBuilds package repository, which I am using to make sure there is no interference between with Ubuntu kernel packaging)
Comment 3 Franck Routier 2010-03-15 16:42:35 UTC
I have activated debug mode for the module and get a lot of output, but I'm pretty much clueless on what to look at.

Has anyone an idea about what could be causing this massive packet loss and what I should look for to help debugging this ?

Thanks
Comment 4 Franck Routier 2010-03-20 13:34:39 UTC
I also have a lot of these debug messages :

Mar 20 14:11:52 franck-laptop kernel: [ 1198.426727] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
Mar 20 14:11:52 franck-laptop kernel: [ 1198.435059] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
Mar 20 14:11:52 franck-laptop kernel: [ 1198.435083] ath9k: Unable to stop TxDMA. Reset HAL!
Mar 20 14:12:45 franck-laptop kernel: [ 1251.547125] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
Mar 20 14:12:45 franck-laptop kernel: [ 1251.547230] ath9k: Unable to stop TxDMA. Reset HAL!
Mar 20 14:13:34 franck-laptop kernel: [ 1300.568862] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
Mar 20 14:13:34 franck-laptop kernel: [ 1300.568936] ath9k: Unable to stop TxDMA. Reset HAL!

Maybe there is a relationship ?
Comment 5 DarkStang 2010-04-21 23:48:12 UTC
I am having a very similar issue. I have a Sony VPCCW21FX laptop with an AR9285 wireless card in it. I will be online, and everything is okay. Then a few seconds later my laptop's connection is lagging. Then it's back to normal. Then lagging. Sometimes I will be disconnected from the router and it will reconnect. All the other computers on the network checkout fine.

I don't have much packet loss, however my ping time's range is absolutely horrible. This is the summary from 100 pings to my router via wireless.

100 packets transmitted, 99 received, 1% packet loss, time 99167ms
rtt min/avg/max/mdev = 1.243/74.535/1009.721/256.207 ms, pipe 2

The odd thing is... if I open any application that constantly sends and receives data (bittorrent for example) then everything else runs smoothly. Very little lag, if any, and no dropped connections. Here is another ping summary from while I'm seeding with a bittorrent application.

100 packets transmitted, 100 received, 0% packet loss, time 99134ms
rtt min/avg/max/mdev = 1.179/11.926/537.085/56.051 ms

My average ping time was less than 1/6th that of the original, with MORE network traffic.

I am running the 2.6.32 kernel on a 64 bit system. However I have compiled the ath9k drivers out of the 2.6.32,33, and 34 release candidates and tested. All with the same results.
Comment 6 DarkStang 2010-04-30 02:38:05 UTC
I have uploaded these two videos to help people understand what's happening... They are videos of me running speed tests, with Gnome's system monitor opened up so you can view the network activity history.

This first test is without a bittorrent application open. Notice how the connection comes and goes in random spurts. Anywhere from absolutely no data being received, to over 1MB/s.
http://darkstang.com/vids/no-qb-test.ogv

Now this next video is with qbittorrent open, and I'm downloading/seeding some random Ubuntu .iso's. The connection stays solid the entire time.
http://darkstang.com/vids/with-qb-test.ogv

I feel as though I should also mention, there never appears to be an issue with my laptop sending data, only receiving data. I've noticed this several times during file sharing with other computers on the network and gaming with other computers online or on the network.

Hope this helps...
Comment 7 DarkStang 2010-05-11 02:33:14 UTC
Okay, so I think I have found the issue. It has nothing to do with the ath9k drivers, it appear to have everything to do with the stock kernel that came with my Linux distro. How that works, I don't know. After finals today I had some time to kill so I downloaded and compiled the 2.6.33 kernel. After some initial tests everything seems to be working fine. I will continue to use this over the next week to see how it goes.
Comment 8 John W. Linville 2010-06-02 14:40:12 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=592735
Comment 9 Franck Routier 2010-06-03 07:46:51 UTC
Replying to comment #7, I confirm the problem STILL exists for me with 2.6.33 stock kernel. Comment #8 shows I'm not the only one, which is a bit reassuring for me.

I still don't know what complementary information I could provide to help fix this bug...
Comment 10 Vadim Dyadkin 2010-06-18 18:56:51 UTC
I have the same issue with sony vaio vpccw2s1r and. The ath9k is lagging periodicaly, but if there is an AP's ping it works. The chip is AR9285, I use Gentoo
Comment 11 Franck Routier 2010-06-23 08:49:29 UTC
Problem still here with 2.6.35-rc3.
Comment 12 John W. Linville 2010-06-23 13:41:07 UTC
Any comment from the ath9k-devel group?
Comment 13 Ronald Weiss 2010-07-06 18:16:54 UTC
Hi. I had the same problem with 2.6.33 kernels in Arch Linux. I used ndiswrapper to work around it. But since I upgraded to 2.6.34 kernel (2.6.34.1 currently), the problem disappeared. I have switched back to using ath9k, and there is no packet loss anymore. I have a HP Compaq Mini 311C netbook with AR9285 wifi card.
Comment 14 John W. Linville 2010-08-13 15:56:43 UTC
Closing on the basis of comment 13.  Please reopen if the problem persists with 2.6.35 (or later) kernels.
Comment 15 Sébastien Wilmet 2010-09-06 10:39:46 UTC
I still have the problem with 2.6.36-rc3 (Sony Vaio VPC-EB1S1E with an Atheros AR9285 card).

I tried ndiswrapper but it's worse.
Comment 16 Franck Routier 2010-09-06 12:20:15 UTC
I also still have the bug with 2.6.35.
Comment 17 Sébastien Wilmet 2010-09-06 13:55:24 UTC
With the latest compat-wireless [1] everything is working fine.

[1] http://linuxwireless.org/en/users/Drivers/ath9k
Comment 18 Franck Routier 2010-09-06 14:41:11 UTC
I am using latest Ubuntu beta with compat-wireless. So it ships with the following ath9k module:

franck@franck-laptop:~$ modinfo ath9k
filename:       /lib/modules/2.6.35-19-generic/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko
license:        Dual BSD/GPL
description:    Support for Atheros 802.11n wireless LAN cards.
author:         Atheros Communications
srcversion:     F512940B820872C31133E06
alias:          pci:v0000168Cd0000002Esv*sd*bc*sc*i*
alias:          pci:v0000168Cd0000002Dsv*sd*bc*sc*i*
alias:          pci:v0000168Cd0000002Csv*sd*bc*sc*i*
alias:          pci:v0000168Cd0000002Bsv*sd*bc*sc*i*
alias:          pci:v0000168Cd0000002Asv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000029sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000027sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000024sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000023sv*sd*bc*sc*i*
depends:        ath9k_hw,mac80211,led-class,ath,cfg80211,ath9k_common
vermagic:       2.6.35-19-generic SMP mod_unload modversions 
parm:           debug:Debugging mask (uint)
parm:           nohwcrypt:Disable hardware encryption (int)


Pinging my network gateway, here is the result:


franck@franck-laptop:~$ ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_req=1 ttl=64 time=34.5 ms
64 bytes from 10.0.0.1: icmp_req=4 ttl=64 time=1.45 ms
64 bytes from 10.0.0.1: icmp_req=5 ttl=64 time=14.9 ms
64 bytes from 10.0.0.1: icmp_req=8 ttl=64 time=1.31 ms
64 bytes from 10.0.0.1: icmp_req=9 ttl=64 time=4.33 ms
64 bytes from 10.0.0.1: icmp_req=10 ttl=64 time=2.29 ms
64 bytes from 10.0.0.1: icmp_req=13 ttl=64 time=3.68 ms
64 bytes from 10.0.0.1: icmp_req=14 ttl=64 time=46.9 ms
64 bytes from 10.0.0.1: icmp_req=17 ttl=64 time=1.44 ms
64 bytes from 10.0.0.1: icmp_req=18 ttl=64 time=78.4 ms
64 bytes from 10.0.0.1: icmp_req=19 ttl=64 time=2.22 ms
64 bytes from 10.0.0.1: icmp_req=22 ttl=64 time=1.66 ms
^C
--- 10.0.0.1 ping statistics ---
22 packets transmitted, 12 received, 45% packet loss, time 21049ms
rtt min/avg/max/mdev = 1.318/16.101/78.406/23.638 ms


So, no, it does not work here...
I have debug enabled, but I don't have a clue about what to do with it...
So here it goes, this is what I find in /sys/kernel/debug:

franck@franck-laptop:~$ sudo cat /sys/kernel/debug/ath9k/phy0/dma 
Raw DMA Debug values:

0: 88888888 1: 00000000 2: 12249249 3: 00000000 
4: 00000000 5: 00000000 6: 00106408 7: 000280c0 

Num QCU: chain_st fsp_ok fsp_st DCU: chain_st
 0           0      1      1            0
 1           0      1      1            0
 2           0      1      1            0
 3           0      1      1            0
 4           0      1      1            0
 5           0      1      1            0
 6           0      1      1            0
 7           0      1      1            0
 8           0      0      1            0
 9           0      0      1            0

qcu_stitch state:    0    qcu_fetch state:         0
qcu_complete state:  0    dcu_complete state:      0
dcu_arb state:       0    dcu_fp state:            0
chan_idle_dur:       2    chan_idle_dur_valid:     1
txfifo_valid_0:      0    txfifo_valid_1:          0
txfifo_dcu_num_0:    3    txfifo_dcu_num_1:        8
pcu observe: 0x2880
AR_CR: 0x4franck@franck-laptop:~$ sudo cat /sys/kernel/debug/ath9k/phy0/interrupt 
      RX:      13491
   RXEOL:          1
   RXORN:          0
      TX:       2138
   TXURN:          0
     MIB:      13459
   RXPHY:          0
   RXKCM:          0
    SWBA:          0
   BMISS:        225
     BNR:          0
     CST:       5865
     GTT:       3588
     TIM:          0
  CABEND:          0
DTIMSYNC:          0
    DTIM:          0
   TOTAL:      37647franck@franck-laptop:~$ sudo cat /sys/kernel/debug/ath9k/phy0/rcstat 
    HT    MCS   Rate    Success    Retries   XRetries        PER
                1.0:          5         35          0          0
                2.0:          3         34         10         14
                5.5:         37        218         16         20
               11.0:         38        326         72         41
                6.0:          0          0          0          0
                9.0:          0          0          0          0
               12.0:         20        297        108         16
               18.0:         46        363        128          0
               24.0:         73        505        140         10
               36.0:         76        354        160         27
               48.0:        139        395        180         27
               54.0:        562        393        142         28
franck@franck-laptop:~$ sudo cat /sys/kernel/debug/ath9k/phy0/recv 
           CRC ERR :        398
   DECRYPT CRC ERR :          0
           PHY ERR :          1
           MIC ERR :          0
 PRE-DELIM CRC ERR :          0
POST-DELIM CRC ERR :          0
  DECRYPT BUSY ERR :          0
          UNDERRUN :          0
            TIMING :          0
            PARITY :          0
              RATE :          0
            LENGTH :          1
             RADAR :          0
           SERVICE :          0
               TOR :          0
       OFDM-TIMING :          0
OFDM-SIGNAL-PARITY :          0
         OFDM-RATE :          0
       OFDM-LENGTH :          0
   OFDM-POWER-DROP :          0
      OFDM-SERVICE :          0
      OFDM-RESTART :          0
   FALSE-RADAR-EXT :          0
        CCK-TIMING :          0
    CCK-HEADER-CRC :          0
          CCK-RATE :          0
       CCK-SERVICE :          0
       CCK-RESTART :          0
        CCK-LENGTH :          0
    CCK-POWER-DROP :          0
            HT-CRC :          0
         HT-LENGTH :          0
           HT-RATE :          0

franck@franck-laptop:~$ sudo cat /sys/kernel/debug/ath9k/phy0/regidx 
0x00000000

franck@franck-laptop:~$ sudo cat /sys/kernel/debug/ath9k/phy0/regval 
0x00000000

franck@franck-laptop:~$ sudo cat /sys/kernel/debug/ath9k/phy0/rx_chainmask 
0x00000001

franck@franck-laptop:~$ sudo cat /sys/kernel/debug/ath9k/phy0/tx_chainmask 
0x00000001
franck@franck-laptop:~$ sudo cat /sys/kernel/debug/ath9k/phy0/wiphy 
primary: phy0 (ACTIVE chan=10 ht=0)
addr: 2c:81:58:e8:d7:20
addrmask: ff:ff:ff:ff:ff:ff




franck@franck-laptop:~$ sudo cat /sys/kernel/debug/ath9k/phy0/xmit 
                            BE         BK        VI        VO

MPDUs Queued:              961          0         0       521
MPDUs Completed:           961          0         0       521
Aggregates:                  0          0         0         0
AMPDUs Queued:               0          0         0         0
AMPDUs Completed:            0          0         0         0
AMPDUs Retried:              0          0         0         0
AMPDUs XRetried:             0          0         0         0
FIFO Underrun:               0          0         0         0
TXOP Exceeded:               0          0         0         0
TXTIMER Expiry:              0          0         0         0
DESC CFG Error:              0          0         0         0
DATA Underrun:               0          0         0         0
DELIM Underrun:              0          0         0         0
Comment 19 Vadim Dyadkin 2010-09-06 18:00:39 UTC
I also have the same bug with 2.6.35 and sony vaio vpccw2s1r (ath9285). I have to use madwifi, but it's really unstable.
Comment 20 Gavin Graham 2010-09-13 20:09:54 UTC
FWIW, I was having the exact same issues with the beta of Ubuntu 10.10.

I've just downloaded and installed the ath9k module from 'compat-wireless-2010-09-12' and it seems after 30min of testing that my problem may be resolved. I will report back after more testing.
Comment 21 Franck Routier 2010-09-14 09:29:06 UTC
I am the initial reporter, and I can confirm that compat-wireless-2010-09-12 seems to solve the issue for me.
I'll test for the rest of the day and go back, but I'm quite optimistic so far, after 30 min testing.

I tried to look at the changelogs but couldn't find what made the difference... the point is that I'm probably not competent enough to find it. Does anyone have an idea of what the problem could have been and what (seemingly) fixed it ?
Comment 22 Gavin Graham 2010-09-14 12:16:45 UTC
Well nearing 24hours later and 'compat-wireless-2010-09-12' has certainly fixed my wifi dropouts.
Comment 23 Vadim Dyadkin 2010-09-17 23:23:15 UTC
For me it also seems to be fixed with compat-wireless-2010-09-12 and last 2.6.35
Comment 24 Michel Alexandre Salim 2010-10-17 18:28:02 UTC
I experience the same problem on my Sony Vaio netbook (VPCW21C5E) running Fedora, with both the latest F-13 and F-14 kernels:

kernel-2.6.34.7-56.fc13.x86_64
kernel-2.6.35.6-43.fc14.x86_64

and the Atheros AR9285

02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)


as DarkStang noted, keeping a high frequency of network activity helps. I set up a permanent ping of my local AP, and start a large download, and notice that whenever I stop the ping session, wget switches from updating the download rate several times a second to updating every second, and the speed starts dropping (sometimes all the way to stalling) during the next several seconds. Restarting the ping session causes the download speed to gradually recover.
Comment 25 Michel Alexandre Salim 2010-10-17 18:50:25 UTC
Confirmed that compat-wireless-2010-09-12 fixes this problem. I'd also note that my other Vaio laptop, with the same reported network card, has never suffered from the network connectivity problem at all, so it's probably due to how hardware makers customize these devices (similar to how there is a different Intel HDA audio wiring on every laptop out there!)

With the drivers from the patch I get > 250 KB/s download speed, without pinging, from mirror.kernel.org, and I was only getting around 150 KB/s with the driver shipped with 2.6.35.6 even with a ping session permanently active

Suggest that this bug is kept open until whatever changes were added to compat-wireless up to 20100912 that has not been merged upstream, are merged. From the kernel changelogs for 2.6.36-rc releases there don't seem to be many ath9k changes (rc2, rc4, rc8)
Comment 26 Mike Okun 2010-10-21 11:33:21 UTC
I am experiencing connection problems using Gentoo 2.6.35-r6 with AR9285 chipset (Zotac NM10 motherboard) in master mode. 
Actually wifi works pretty well in the immediate vicinity of AR9285 antenna, but if the distance is about 2-3m connection is lost, while signal strength reported by notebook is still "excelent" or "very good".
I have tested with Sony Vaio Z51 (Intel 5100ABG) and Goolge Nexus phone. I have tried ath9k from kernel sources, compat-wireless-2.6.35-1 and compat-wireless-2010-10-20.

lscpi:
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
        Subsystem: Device 1a3b:1089
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 19
        Region 0: Memory at febf0000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
                Address: 00000000  Data: 0000
        Capabilities: [60] Express (v2) Legacy Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
                        ClockPM- Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Not Supported, TimeoutDis+
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
                         Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB
        Capabilities: [100] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
        Capabilities: [140] Virtual Channel <?>
        Capabilities: [160] Device Serial Number 00-15-17-ff-ff-24-14-12
        Capabilities: [170] Power Budgeting <?>
        Kernel driver in use: ath9k
        Kernel modules: ath9k


iwconfig:

wlan0     IEEE 802.11bgn  Mode:Master  Frequency:2.462 GHz  Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
Comment 27 Michel Alexandre Salim 2010-11-01 20:43:45 UTC
(In reply to comment #25)
> Confirmed that compat-wireless-2010-09-12 fixes this problem. I'd also note
> that my other Vaio laptop, with the same reported network card, has never
> suffered from the network connectivity problem at all, so it's probably due
> to
> how hardware makers customize these devices (similar to how there is a
> different Intel HDA audio wiring on every laptop out there!)
> 

Note that on my other laptop (Vaio VPC-EB1M1E), supposedly the same AR9285, compat-wireless-20100912 actually behaves much *worse*; the network becomes unreachable within a couple of minutes. Whereas it normally has no problem with the built-in kernel Atheros drivers (on both F-13 and F-14) but after a couple of days of heavy traffic, I do have to reload the entire wireless stack

This is with Fedora 14's kernel-2.6.35.6-48.fc14.x86_64
Comment 28 John W. Linville 2010-11-23 18:34:24 UTC
I'm closing this bug for the following reasons:

   -- it is vague from the beginning;
   -- too many "me too" reports make it unclear if this is a single problem;
   -- not clear whether current code fixes the issue(s) in this report or not.

If you still think you have a bug requiring attention, please open a new bug for your _specific_ issue.  Please do _not_ reopen this one, as it is now hopelessly confused and therefore useless.

Note You need to log in before you can comment on or make changes to this bug.