[lucid regression] Acer Aspire ONE, Atheros AR5001/AR5007 (168c:001c) frequently causes all AP clients to disassociate

Bug #374265 reported by András Korn on 2009-05-09
80
This bug affects 14 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

Hi,

I installed the jaunty "netbook remix" on my new Acer Aspire ONE. I noticed that my wifi connection was unstable to the point that even apt-get would sometimes fail to download some packages. Reported signal levels were around 40% in a room where a Lenovo T61 with an Intel wifi adapter was reporting 70+%. Playing media from an nfs share was impossible; the connection would start going away after 2-3 minutes. Even lengthy terminal output in an ssh session was enough to cause the connection to be dropped for a few seconds. Significant upstream traffic kills the connection almost instantly, even when the rate is limited to 1Mbps. The kernel log contained lines like "ath5k phy0: unsupported jumbo", but I read that these messages were benign. Additionally, the following was logged:

May 9 13:01:53 cherub kernel: [ 478.120915] ath5k phy0: unsupported jumbo
May 9 13:02:38 cherub kernel: [ 523.132095] wlan0: no probe response from AP 00:0d:88:c9:04:7f - disassociating
May 9 13:02:39 cherub kernel: [ 524.451738] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:02:39 cherub kernel: [ 524.453292] wlan0: authenticated
May 9 13:02:39 cherub kernel: [ 524.453304] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:02:39 cherub kernel: [ 524.455771] wlan0: RX ReassocResp from 00:0d:88:c9:04:7f (capab=0x431 status=0 aid=36)
May 9 13:02:39 cherub kernel: [ 524.455784] wlan0: associated
May 9 13:02:47 cherub kernel: [ 532.466673] wlan0: deauthenticated (Reason: 14)
May 9 13:02:48 cherub kernel: [ 533.468165] wlan0: direct probe to AP 00:0d:88:c9:04:7f try 1
May 9 13:02:48 cherub kernel: [ 533.470573] wlan0 direct probe responded
May 9 13:02:48 cherub kernel: [ 533.470584] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:02:48 cherub kernel: [ 533.472694] wlan0: authenticated
May 9 13:02:48 cherub kernel: [ 533.472702] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:02:48 cherub kernel: [ 533.474883] wlan0: RX ReassocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:02:48 cherub kernel: [ 533.474895] wlan0: AP denied association (code=12)
May 9 13:02:49 cherub kernel: [ 533.672099] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:02:49 cherub kernel: [ 533.674290] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:02:49 cherub kernel: [ 533.674303] wlan0: AP denied association (code=12)
May 9 13:02:49 cherub kernel: [ 533.872103] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:02:49 cherub kernel: [ 533.874273] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:02:49 cherub kernel: [ 533.874285] wlan0: AP denied association (code=12)
May 9 13:02:49 cherub kernel: [ 534.072078] wlan0: association with AP 00:0d:88:c9:04:7f timed out
May 9 13:02:50 cherub kernel: [ 535.300607] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:02:50 cherub kernel: [ 535.302079] wlan0: authenticated
May 9 13:02:50 cherub kernel: [ 535.302094] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:02:50 cherub kernel: [ 535.305217] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:02:50 cherub kernel: [ 535.305233] wlan0: AP denied association (code=12)
May 9 13:02:50 cherub kernel: [ 535.502579] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:02:50 cherub kernel: [ 535.504841] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:02:50 cherub kernel: [ 535.504855] wlan0: AP denied association (code=12)
May 9 13:02:51 cherub kernel: [ 535.700109] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:02:51 cherub kernel: [ 535.702330] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:02:51 cherub kernel: [ 535.702347] wlan0: AP denied association (code=12)
May 9 13:02:51 cherub kernel: [ 535.900124] wlan0: association with AP 00:0d:88:c9:04:7f timed out
May 9 13:03:02 cherub kernel: [ 546.520042] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:02 cherub kernel: [ 546.521782] wlan0: authenticated
May 9 13:03:02 cherub kernel: [ 546.521793] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:02 cherub kernel: [ 546.527902] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:02 cherub kernel: [ 546.527915] wlan0: AP denied association (code=12)
May 9 13:03:02 cherub kernel: [ 546.624094] wlan0: deauthenticating by local choice (reason=3)
May 9 13:03:02 cherub kernel: [ 546.937792] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 9 13:03:02 cherub kernel: [ 546.990485] wlan0: deauthenticating by local choice (reason=3)
May 9 13:03:02 cherub kernel: [ 547.184951] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 9 13:03:03 cherub kernel: [ 548.391983] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:03 cherub kernel: [ 548.393520] wlan0: authenticated
May 9 13:03:03 cherub kernel: [ 548.393532] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:03 cherub kernel: [ 548.395837] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:03 cherub kernel: [ 548.395849] wlan0: AP denied association (code=12)
May 9 13:03:04 cherub kernel: [ 548.593065] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:04 cherub kernel: [ 548.595249] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:04 cherub kernel: [ 548.595261] wlan0: AP denied association (code=12)
May 9 13:03:04 cherub kernel: [ 548.793115] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:04 cherub kernel: [ 548.795347] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:04 cherub kernel: [ 548.795364] wlan0: AP denied association (code=12)
May 9 13:03:04 cherub kernel: [ 548.992090] wlan0: association with AP 00:0d:88:c9:04:7f timed out
May 9 13:03:08 cherub kernel: [ 552.613402] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:08 cherub kernel: [ 552.614954] wlan0: authenticated
May 9 13:03:08 cherub kernel: [ 552.614965] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:08 cherub kernel: [ 552.617606] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:08 cherub kernel: [ 552.617617] wlan0: AP denied association (code=12)
May 9 13:03:08 cherub kernel: [ 552.812080] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:08 cherub kernel: [ 552.814228] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:08 cherub kernel: [ 552.814244] wlan0: AP denied association (code=12)
May 9 13:03:08 cherub kernel: [ 553.012125] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:08 cherub kernel: [ 553.014367] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:08 cherub kernel: [ 553.014389] wlan0: AP denied association (code=12)
May 9 13:03:08 cherub kernel: [ 553.212062] wlan0: association with AP 00:0d:88:c9:04:7f timed out
May 9 13:03:13 cherub kernel: [ 557.677071] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:13 cherub kernel: [ 557.678623] wlan0: authenticated
May 9 13:03:13 cherub kernel: [ 557.678633] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:13 cherub kernel: [ 557.681074] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:13 cherub kernel: [ 557.681086] wlan0: AP denied association (code=12)
May 9 13:03:13 cherub kernel: [ 557.880124] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:13 cherub kernel: [ 557.884145] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:13 cherub kernel: [ 557.884156] wlan0: AP denied association (code=12)
May 9 13:03:13 cherub kernel: [ 558.076090] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:13 cherub kernel: [ 558.078414] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:13 cherub kernel: [ 558.078430] wlan0: AP denied association (code=12)
May 9 13:03:13 cherub kernel: [ 558.276067] wlan0: association with AP 00:0d:88:c9:04:7f timed out
May 9 13:03:18 cherub kernel: [ 562.834670] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:18 cherub kernel: [ 562.836422] wlan0: authenticated
May 9 13:03:18 cherub kernel: [ 562.836434] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:18 cherub kernel: [ 562.838473] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:18 cherub kernel: [ 562.838583] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:18 cherub kernel: [ 562.840268] wlan0: authenticated
May 9 13:03:18 cherub kernel: [ 562.840280] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:18 cherub kernel: [ 562.843946] wlan0: deauthenticated (Reason: 6)
May 9 13:03:19 cherub kernel: [ 563.841078] wlan0: direct probe to AP 00:0d:88:c9:04:7f try 1
May 9 13:03:19 cherub kernel: [ 563.843479] wlan0 direct probe responded
May 9 13:03:19 cherub kernel: [ 563.843492] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:19 cherub kernel: [ 563.846055] wlan0: authenticated
May 9 13:03:19 cherub kernel: [ 563.846067] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:19 cherub kernel: [ 563.848172] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:19 cherub kernel: [ 563.848185] wlan0: AP denied association (code=12)
May 9 13:03:19 cherub kernel: [ 564.045105] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:19 cherub kernel: [ 564.047965] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:19 cherub kernel: [ 564.047986] wlan0: AP denied association (code=12)
May 9 13:03:19 cherub kernel: [ 564.244141] wlan0: association with AP 00:0d:88:c9:04:7f timed out
May 9 13:03:24 cherub kernel: [ 568.962230] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:24 cherub kernel: [ 568.963788] wlan0: authenticated
May 9 13:03:24 cherub kernel: [ 568.963802] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:24 cherub kernel: [ 568.966168] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:24 cherub kernel: [ 568.966184] wlan0: AP denied association (code=12)
May 9 13:03:24 cherub kernel: [ 569.161074] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:24 cherub kernel: [ 569.163213] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:24 cherub kernel: [ 569.163229] wlan0: AP denied association (code=12)
May 9 13:03:24 cherub kernel: [ 569.362820] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:24 cherub kernel: [ 569.364987] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:24 cherub kernel: [ 569.365008] wlan0: AP denied association (code=12)
May 9 13:03:25 cherub kernel: [ 569.564140] wlan0: association with AP 00:0d:88:c9:04:7f timed out
May 9 13:03:29 cherub kernel: [ 574.099581] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:29 cherub kernel: [ 574.101157] wlan0: authenticated
May 9 13:03:29 cherub kernel: [ 574.101166] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:29 cherub kernel: [ 574.103648] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:29 cherub kernel: [ 574.103658] wlan0: AP denied association (code=12)
May 9 13:03:29 cherub kernel: [ 574.300235] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:29 cherub kernel: [ 574.302363] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:29 cherub kernel: [ 574.302377] wlan0: AP denied association (code=12)
May 9 13:03:29 cherub kernel: [ 574.501725] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:29 cherub kernel: [ 574.503858] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:29 cherub kernel: [ 574.503874] wlan0: AP denied association (code=12)
May 9 13:03:30 cherub kernel: [ 574.700064] wlan0: association with AP 00:0d:88:c9:04:7f timed out
May 9 13:03:34 cherub kernel: [ 579.179020] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:34 cherub kernel: [ 579.181052] wlan0: authenticated
May 9 13:03:34 cherub kernel: [ 579.181063] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:34 cherub kernel: [ 579.183758] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:34 cherub kernel: [ 579.183770] wlan0: AP denied association (code=12)
May 9 13:03:34 cherub kernel: [ 579.380055] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:34 cherub kernel: [ 579.382154] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:34 cherub kernel: [ 579.382163] wlan0: AP denied association (code=12)
May 9 13:03:35 cherub kernel: [ 579.580392] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:35 cherub kernel: [ 579.582508] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:35 cherub kernel: [ 579.582520] wlan0: AP denied association (code=12)
May 9 13:03:35 cherub kernel: [ 579.780062] wlan0: association with AP 00:0d:88:c9:04:7f timed out
May 9 13:03:39 cherub kernel: [ 584.299407] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:39 cherub kernel: [ 584.300962] wlan0: authenticated
May 9 13:03:39 cherub kernel: [ 584.300974] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:39 cherub kernel: [ 584.303268] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:39 cherub kernel: [ 584.303282] wlan0: AP denied association (code=12)
May 9 13:03:39 cherub kernel: [ 584.500068] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:39 cherub kernel: [ 584.502432] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:39 cherub kernel: [ 584.502449] wlan0: AP denied association (code=12)
May 9 13:03:40 cherub kernel: [ 584.700080] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:40 cherub kernel: [ 584.702260] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:40 cherub kernel: [ 584.702273] wlan0: AP denied association (code=12)
May 9 13:03:40 cherub kernel: [ 584.901734] wlan0: association with AP 00:0d:88:c9:04:7f timed out
May 9 13:03:44 cherub kernel: [ 589.349249] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:44 cherub kernel: [ 589.354920] wlan0: authenticated
May 9 13:03:44 cherub kernel: [ 589.354932] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:44 cherub kernel: [ 589.357211] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:44 cherub kernel: [ 589.357224] wlan0: AP denied association (code=12)
May 9 13:03:45 cherub kernel: [ 589.552049] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:45 cherub kernel: [ 589.554146] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:45 cherub kernel: [ 589.554155] wlan0: AP denied association (code=12)
May 9 13:03:45 cherub kernel: [ 589.756063] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:45 cherub kernel: [ 589.758225] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=12 aid=0)
May 9 13:03:45 cherub kernel: [ 589.758239] wlan0: AP denied association (code=12)
May 9 13:03:45 cherub kernel: [ 589.952075] wlan0: association with AP 00:0d:88:c9:04:7f timed out
May 9 13:03:49 cherub kernel: [ 594.456558] wlan0: authenticate with AP 00:0d:88:c9:04:7f
May 9 13:03:49 cherub kernel: [ 594.458090] wlan0: authenticated
May 9 13:03:49 cherub kernel: [ 594.458101] wlan0: associate with AP 00:0d:88:c9:04:7f
May 9 13:03:49 cherub kernel: [ 594.460796] wlan0: RX AssocResp from 00:0d:88:c9:04:7f (capab=0x431 status=0 aid=36)
May 9 13:03:49 cherub kernel: [ 594.460806] wlan0: associated
May 9 13:03:49 cherub kernel: [ 594.463050] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 9 13:04:00 cherub kernel: [ 604.832073] wlan0: no IPv6 routers present
May 9 13:10:01 cherub kernel: [ 966.448500] ath5k phy0: unsupported jumbo

I upgraded to karmic, but had the same problem with the ath5k driver in the 2.6.30-2 kernel that ships with it.

In order to rule out a hardware defect, I compiled madwifi HEAD (r4020) and tried with that, and so far the connection seems to be stable (although reported signal levels are still pretty low). This leads me to believe that this is a bug in the ath5k driver, which is why I'm filing the report against linux-image-generic.

When the ath5k card disconnects as shown above, my other notebook, a Thinkpad with an iwlagn card, is also disconnected; it's almost as if the ath5k driver would confuse the AP or other wireless clients in range so much that they can't re-associate for up to a minute.

I only tested with a single Micronet AP, with WPA-PSK.

The relevant bit from lspci is this:

03:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01)
        Subsystem: Foxconn International, Inc. Device [105b:e008]
        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 18
        Region 0: Memory at 55200000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
                Address: 00000000 Data: 0000
        Capabilities: [60] Express (v1) 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- Suprise- LLActRep- BwNot-
                LnkCtl: ASPM L0s L1 Enabled; RCB 128 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
                Vector table: BAR=0 offset=00000000
                PBA: BAR=0 offset=00000000
        Capabilities: [100] Advanced Error Reporting <?>
        Capabilities: [140] Virtual Channel <?>
        Kernel driver in use: ath_pci
        Kernel modules: ath_pci, ath5k

The ath5k driver in 2.6.30-2-generic detected the card thusly:

[ 11.178534] acer-wmi: Acer Laptop ACPI-WMI Extras
[ 11.178543] acer-wmi: Blacklisted hardware detected - not loading
[ 11.255946] ath5k 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 11.256066] ath5k 0000:03:00.0: setting latency timer to 64
[ 11.256171] ath5k 0000:03:00.0: registered as 'phy0'
[ 11.328587] phy0: Selected rate control algorithm 'minstrel'
[ 11.474710] Registered led device: ath5k-phy0::rx
[ 11.474751] Registered led device: ath5k-phy0::tx
[ 11.474759] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)

When using madwifi, I see:

[ 11.544193] ath_pci 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 11.544259] ath_pci 0000:03:00.0: setting latency timer to 64
[...]
[ 11.889459] acer-wmi: Acer Laptop ACPI-WMI Extras
[ 11.889469] acer-wmi: Blacklisted hardware detected - not loading
[ 12.062080] MadWifi: ath_attach: Switching rfkill capability off.
[ 12.095518] wifi0: Atheros AR2425 chip found (MAC 14.2, PHY SChip 7.0, Radio 10.2)
[ 12.136177] ath_pci: wifi0: Atheros 5424/2424: mem=0x55200000, irq=18

Andras

Andy Whitcroft (apw) wrote :

This is not a bug in the linux-meta package, moving to the linux package.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
András Korn (kornandras) wrote :

This is just to let you know that the problem is still present in 2.6.31-3-generic, even when using a bitrate of 1Mbps.

My connection wasn't entirely stable with madwifi either, but the error messages were different (unfortunately, I no longer have them, but I can certainly try madwifi once more if you tell me it makes sense).

Andras

András Korn (kornandras) wrote :

FWIW, this appears to be the same problem (at least it produces the same symptoms) as http://madwifi-project.org/ticket/1773 and http://bugzilla.kernel.org/show_bug.cgi?id=10605 (the latter is supposedly fixed though).

I added new pertinent information to http://bugzilla.kernel.org/show_bug.cgi?id=10605#c9.

Summary: the ath5k problem also causes other clients to be disconnected from the same AP. It appears to be triggered by significant upstream traffic from the Atheros card.

Andras

description: updated
summary: - Acer Aspire ONE, Atheros AR242x frequent connection interruptions when
- more than light traffic; madwifi works
+ Acer Aspire ONE, Atheros AR5001 (168c:001c) frequently causes all AP
+ clients to disassociate

AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: steve 1173 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x58540000 irq 16'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,1025015b,00100101'
   Controls : 9
   Simple ctrls : 6
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=a9690981-13d8-469e-b131-fc84a85a27c0
MachineType: Acer AOA110
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=1b688410-a82b-487b-958b-e5a644ac6da8 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_CA.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-11-generic N/A
 linux-firmware 1.19
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/09/2008
dmi.bios.vendor: Acer
dmi.bios.version: v0.3114
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrv0.3114:bd05/09/2008:svnAcer:pnAOA110:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AOA110
dmi.product.version: 1
dmi.sys.vendor: Acer

Changed in linux (Ubuntu):
status: New → Triaged
tags: added: apport-collected

I am confirming this, a fresh Karmic beta install showed the same problem.

Changed in linux (Ubuntu):
importance: Undecided → Medium
Zbigniew Zemła (zbigniew) wrote :

I also confirm this. The same problem on Karmic Beta with Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01) on Samsung R522 laptop

Antonio (a--candela) wrote :

i also confirm this problem on Toshiba NB 100 with Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01).

Also affects Lucid, frequent disconnects, difficult to connect to AP too. This is with AR5007, same chipset, same driver.

tags: added: compat-wireless lucid
summary: - Acer Aspire ONE, Atheros AR5001 (168c:001c) frequently causes all AP
- clients to disassociate
+ [lucid regression] Acer Aspire ONE, Atheros AR5001 (168c:001c)
+ frequently causes all AP clients to disassociate
tags: added: regression-release
removed: compat-wireless lucid
ibidem (ibid-ag) wrote :

I have not seen this issue; running Lucid (2.6.32-9 &2.6.32-10) Alpha on an Acer Aspire One (ZG5) with AR5007 chipset; using Wicd for wireless.
Wireless connection has been reliable so far.

I beg to differ with ibidem, I am seeing this in Lucid, and at times as with Jaunty and Karmic, there are times when it even becomes near impossible to connect to the AP.

Gavin McCullagh (gmccullagh) wrote :

I have an acer aspire one running lucid and am regularly losing my wireless link. I then click the network-manager and reconnect it but it's pretty inconvenient. There aren't any obvious messages in syslog or messages or dmesg which correspond to the link dropping.

gavinmc@teenie:~$ apt-cache policy linux-image wireless-tools libiw30
linux-image:
  Installed: (none)
  Candidate: 2.6.32.11.11
  Version table:
     2.6.32.11.11 0
        500 http://ie.archive.ubuntu.com lucid/main Packages
wireless-tools:
  Installed: 30~pre9-3ubuntu1
  Candidate: 30~pre9-3ubuntu1
  Version table:
 *** 30~pre9-3ubuntu1 0
        500 http://ie.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status
libiw30:
  Installed: 30~pre9-3ubuntu1
  Candidate: 30~pre9-3ubuntu1
  Version table:
 *** 30~pre9-3ubuntu1 0
        500 http://ie.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

Gavin McCullagh (gmccullagh) wrote :

The relevant chunk from lspci -v is:

03:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
        Subsystem: Foxconn International, Inc. Device e008
        Flags: bus master, fast devsel, latency 0, IRQ 18
        Memory at 55200000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
        Capabilities: [60] Express Legacy Endpoint, MSI 00
        Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
        Capabilities: [100] Advanced Error Reporting <?>
        Capabilities: [140] Virtual Channel <?>
        Kernel driver in use: ath5k
        Kernel modules: ath5k

ArmiDuctor (armiductor) wrote :

I have the same problem as Gavin on my aa1 which also has is the AR5001. Only problem I have is that after it loses its connection it is unable to connect anymore. It is as if you use the enable/disable switch on the enclosure to switch off wireless and after that it wont respond to enabling it again. As a workaround i reboot in windows that enables the wireless again and after that reboot back to lucid. So it looks to me that the controller goes into a sleep-mode and that the driver is unable to wake it up again.

ibidem (ibid-ag) wrote :

Well, now I'm seeing the dropping connection issue (not causing all clients to drop, though)
IMHO, this is a separate issue.
I can't file a bug report just now, since I'm still at kernel 2.6.32-12.
Gavin, Armiductor:
Try running "iwconfig" when the connection drops, and look at the essid--for me, it's always corrupted at that point.
Using iwconfig generally fixes it, with a bit of work.

Brent N. (brent-nesbitt) wrote :

I can confirm this probem on my AAOne running lucid beta-1. It was also present in Karmic, but I was able to use madwifi instead, which resolved the issue.

I have not been able to get madwifi working in lucid yet.

Bob Clough (parag0n) wrote :

Confirming this on AA1 AOA150, running latest lucid as of last night. 99% of the time it'll be fine, but when i try to do lots of data transfer (streaming video, downloading files, apt update) it'll work for a minute or so, then die, and not work again until i reconnect the wireless.

This has happened on two different routers, a WRT54G running Tomato, and a BeBox (speedtouch 585 i think).

Same laptop, same routers worked fine in karmic.

David O'C (docindustries) wrote :

I am confirming this bug on my Aspire one AOA150, I have the exact same symptoms that Bob has mentioned. I am running Ubuntu 10.04 beta 1.

summary: - [lucid regression] Acer Aspire ONE, Atheros AR5001 (168c:001c)
+ [lucid regression] Acer Aspire ONE, Atheros AR5001/AR5007 (168c:001c)
frequently causes all AP clients to disassociate
András Korn (kornandras) wrote :

People who have commented on this bug, please also submit any _new_ relevant information to https://bugzilla.kernel.org/show_bug.cgi?id=13892 because Ubuntu/Canonical apparently doesn't have the resources to really do anything here, and the kernel people seem to think more information is needed.

Actually, since Canonical/Ubuntu do not produce or code the kernel, and take it from upstream, it seems fitting that they're told about it and that they fix it, considering this will fix all other linux distros in the case of the kernel......

I have just noticed this is already filed as a metabug of all of the other Atheros chipset issues, so this is being marked as a duplicate of bug 461419. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Changed in linux (Ubuntu):
status: Triaged → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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