linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miek Gieben <miek@miek.nl>
To: linux-wireless@vger.kernel.org
Subject: Frequent disconnects with ath9k
Date: Thu, 12 Jul 2012 08:58:06 +0200	[thread overview]
Message-ID: <20120712065805.GA15967@miek.nl> (raw)

[-- Attachment #1: Type: text/plain, Size: 4933 bytes --]

Hello,

I'm experiencing frequent disconnects with the ath9k driver and the 
AR9485 wireless adapter. This Ubuntu bug report has more information:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/773154

I've tried:
* Newer kernels, from stock Ubuntu 12.04, through 3.4.x and staying with 3.5-rc6
    now. All kernels show the same problem, although is seems to get better
    (less disconnects). Running 3.5-rc6 atm.

* Switched with wicd, seems to help. The background scanning of network manager
    makes things worse.

* Disabled power management: does not help (at least in the newer kernels it
    has no effect, in some older ones (<3.2.0) is sort of looked like it did
    something.

* Disable the hw encryption: didn't help.

* Disabled 'ani' (don't know what that is, but it didn't help).

* Disabled ipv6: didn't help.

Things that seems related to the disconnects:

* Noisy environment, multiple access points in the neighborhood with the
    same SSID.

* The background scanning from network-manager. With wicd the situation
    is much more tolerable.

* After a sleep/resume cycle is seems worse.

Does someone know what the issue might be? Please CC me on any replies - I'm not
subscribed to this list.

Below is a trace from my kernel log, which shows a disconnect:

[ 1453.116807] wlan0: RX AssocResp from 28:10:xx:xx:xx:xx (capab=0x431 status=0 aid=2)                                                    
[ 1453.116818] wlan0: associated                                                                                                          
[ 2177.242371] cfg80211: All devices are disconnected, going to restore regulatory settings                                               
[ 2177.242387] cfg80211: Restoring regulatory settings                                                                                    
[ 2177.242396] cfg80211: Calling CRDA to update world regulatory domain                                                                   
[ 2177.246070] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain                   
[ 2177.249079] cfg80211: World regulatory domain updated:                                                                                 
[ 2177.249084] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)                                              
[ 2177.249089] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)                                                   
[ 2177.249094] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)                                                   
[ 2177.249098] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)                                                   
[ 2177.249102] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)                                                   
[ 2177.249106] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)                                                   
[ 2177.615761] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready                                                                        
[ 2180.097436] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready                                                                        
[ 2182.905090] wlan0: authenticate with 28:10:xx:xx:xx:xx                                                                                 
[ 2182.913345] wlan0: send auth to 28:10:xx:xx:xx:xx (try 1/3)                                                                            
[ 2182.915536] wlan0: authenticated                                                                                                       
[ 2182.924019] wlan0: associate with 28:10:xx:xx:xx:xx (try 1/3)                                                                          
[ 2182.927029] wlan0: RX AssocResp from 28:10:xx:xx:xx:xx (capab=0x431 status=0 aid=2)                                                    
[ 2182.927040] wlan0: associated                                                                                                          
[ 2182.927857] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready                                                                   
[ 2182.928095] cfg80211: Calling CRDA for country: GB                                                                                     
[ 2182.936422] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:                      
[ 2182.936431] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)                                                  

 Kind Regards,

-- 
    Miek Gieben                                                   http://miek.nl

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2012-07-12  7:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12  6:58 Miek Gieben [this message]
2012-07-15 16:46 ` Frequent disconnects with ath9k Yochai Gal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120712065805.GA15967@miek.nl \
    --to=miek@miek.nl \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).