Bug 20922
Summary: | AR9285 connection problem | ||
---|---|---|---|
Product: | Drivers | Reporter: | Mike Okun (list) |
Component: | network-wireless | Assignee: | Atheros developers (ath9k-devel) |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | a.hortelano, alan, linville, marconifabio, mortenbagvendt, senthilkumar, shafi.wireless, trojanowski.ifuj |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.35 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
hostapd.conf
dmesg.log ath debug log |
Description
Mike Okun
2010-10-22 12:52:11 UTC
We shall try to reproduce the issue here and in the mean time, can you please provide us the hostapd config file and also the verbose logs. Also provide the dmesg log. does this issue happen in Open/security? Also were you running any traffic when the failure was noticed and if so what type of traffic. Created attachment 35532 [details]
hostapd.conf
Created attachment 35542 [details]
dmesg.log
I have attached hostapd.conf and dmesg output as you requested. As concerning any special type of traffic I can't select something special, the main reason for disconnect is the distance to AR9285 larger then 0.5-2 m. I have build kernel and compat-wireless with debug and there is no error, fatal log is empty. I will attach it also, may be it can help. Created attachment 35562 [details]
ath debug log
Bug still present in 2.6.37.7 Natty (In reply to comment #6) > Bug still present in 2.6.37.7 Natty You are using it as an AP and disconnection happens only when the distance is increased ? Yes, I am using it as AP. Disconnect is happen when the distance is larger then 1.5-2 m. It is also not possible to connect to AP if the distance is larger then this limit. Hi I also have a problem with the wireless network connection and i'm also on the AR9285. I have already reported my problem at bugs.launchpad - see this: https://bugs.launchpad.net/ubuntu/+bug/668924 In short my problem came with the upgrade from ubuntu 9.10 to 10.04. The problem is still on ubuntu 10.10. The network manager doesn't show the available wireless networks in 10.04 and 10.10. If I boot up in windows or on a live cd with 9.10 (and when I had the 9.10 working) the networks are visible and available. I'm on a HP dv6 2050eo. Regards Morten Hi I'm on Linux Mint 10 on ASUS UL20FT. The chip is also AR9285. I'm experiencing extensive packet loss (30-60%) and association problems (direct probe to xx:xx:xx:xx:xx timed out) while 6-9 meters from AP. speedtest.net yields stuttering transfer which peaks at 1 Mb/s, while all other computers get 15 Mb/s. The problem vanishes when in the same room as the router. Also when the router is set to channel 6 or higher, it won't ever associate. The connection rate given by iwconfig is rarely higher than 1Mb/s. I have tried Ubuntu 10.10 with 2.6.35-27 (same as LM 10), 32 and 64 bit. Same results. The best results were with ndiswrapper and driver 7.7.0.259, but still VERY sensitive to distance from AP. The security is WPA2 Private AES, but WPA and WEP yield the same results. I tried following combinations of kernel and compat-wireless: - 2.6.35-27-generic and ath9k from linux-backports-modules-wireless-maverick-generic and following compat-wireless: - 2010-01-24 - 2010-09-12 - 2010-12-26 - 2011-01-24 - 2011-03-01 - compat-wireless-2.6.35-rc2 - 2.6.38-020638rc6-generic from kernel.ubuntu.com with the following compat-wireless: - compat-wireless-2.6.38-rc4-1 (other wouldn't build) - git trunk of wireless-testing from wireless.kernel.org as of 2011-03-02 All to same results. When FAR FROM AP (~9m, signal ~70%): dmesg: [ 2528.290977] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xf8420000, irq=17 [ 2528.327923] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2529.243442] cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0 [ 2535.937169] wlan0: direct probe to 00:1a:70:df:6c:ad (try 1/3) [ 2536.134409] wlan0: direct probe to 00:1a:70:df:6c:ad (try 2/3) [ 2536.334147] wlan0: direct probe to 00:1a:70:df:6c:ad (try 3/3) [ 2536.533921] wlan0: direct probe to 00:1a:70:df:6c:ad timed out [ 2547.011076] wlan0: direct probe to 00:1a:70:df:6c:ad (try 1/3) [ 2547.014426] wlan0: direct probe responded [ 2547.038557] wlan0: authenticate with 00:1a:70:df:6c:ad (try 1) [ 2547.236324] wlan0: authenticate with 00:1a:70:df:6c:ad (try 2) [ 2547.436082] wlan0: authenticate with 00:1a:70:df:6c:ad (try 3) [ 2547.635830] wlan0: authentication with 00:1a:70:df:6c:ad timed out [ 2558.089096] wlan0: direct probe to 00:1a:70:df:6c:ad (try 1/3) [ 2558.286349] wlan0: direct probe to 00:1a:70:df:6c:ad (try 2/3) [ 2558.486096] wlan0: direct probe to 00:1a:70:df:6c:ad (try 3/3) [ 2558.685851] wlan0: direct probe to 00:1a:70:df:6c:ad timed out iw event -t: 1299147620.563447: wlan0 (phy #0): scan started 1299147621.612001: wlan0 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484, "linksys" 1299147622.254610: wlan0 (phy #0): auth: timed out 1299147622.254685: wlan0 (phy #0): failed to connect to 00:1a:70:df:6c:ad, status: 1: Unspecified failure At this distance a similar setup with Intel wireless on Ubuntu 10:10 works perfectly. When NEAR AP (<9m, signal ~90%): dmesg: [ 1994.902563] wlan0: authenticate with 00:1a:70:df:6c:ad (try 1) [ 1994.904815] wlan0: authenticated [ 1994.904913] wlan0: associate with 00:1a:70:df:6c:ad (try 1) [ 1994.907383] wlan0: RX AssocResp from 00:1a:70:df:6c:ad (capab=0x431 status=0 aid=3) [ 1994.907390] wlan0: associated iw event -t: 1299149713.853438: phy #0: regulatory domain change: set to world roaming by the wireless core upon initialization request 1299149713.955819: wlan0 (phy #0): scan started 1299149714.900739: wlan0 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484, "" 1299149714.926746: wlan0 (phy #0): auth 00:1a:70:df:6c:ad -> 74:f0:6d:97:98:db status: 0: Successful 1299149714.929376: wlan0: new station 00:1a:70:df:6c:ad 1299149714.929836: wlan0 (phy #0): assoc 00:1a:70:df:6c:ad -> 74:f0:6d:97:98:db status: 0: Successful 1299149714.929893: wlan0 (phy #0): connected to 00:1a:70:df:6c:ad Unless the distance is <6m, there is extensive packet loss and frequent disassociation. This happens for all mentioned kernels and versions of ath9k. The most recent I have is the one from git trunk of wireless-testing as of 2011-03-02. modinfo: filename: /lib/modules/2.6.38-rc6-wl/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: F1306F1267D50A98C510E6F alias: pci:v0000168Cd00000032sv*sd*bc*sc*i* alias: pci:v0000168Cd00000030sv*sd*bc*sc*i* 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,cfg80211,ath9k_common,ath vermagic: 2.6.38-rc6-wl SMP mod_unload modversions 686 parm: debug:Debugging mask (uint) parm: nohwcrypt:Disable hardware encryption (int) parm: blink:Enable LED blink on activity (int) parm: btcoex_enable:Enable wifi-BT coexistence (int) iwconfig wlan0 (when associated and ~7m from AP): wlan0 IEEE 802.11bgn ESSID:"linksys" Mode:Managed Frequency:2.412 GHz Access Point: 00:1A:70:DF:6C:AD Bit Rate=1 Mb/s Tx-Power=17 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=64/70 Signal level=-46 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:1001 Invalid misc:1340 Missed beacon:0 I hope this is in any way helpful. I hope this will be fixed soon. As for now, my wife can't enjoy her brand new laptop :( Regards, Karol I have this issue, and I solved it by manually installing the latest compat-wireless. |