All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Martynov <mar.kolya@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Weird error messages in logs
Date: Wed, 2 Feb 2011 23:50:34 -0500	[thread overview]
Message-ID: <AANLkTik90s0FZbg1x_WhJ7h7kbWU7KsdY56rcdWEPL1z@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=dyYCJX5CtKiy0nv7uCWn0nbpRDN9UJ177LP5M@mail.gmail.com>

Hi.

  One more thing I've noticed.
  When I do tcpdump on intel mon interface I get quite a lot of
traffic. When I do same thing on router - I hardly see any traffic. Is
this expected?
  This actually regards problem when client cannot reconnect to router
- in this state even though client send association and authentication
requests it doesn't get response.

  Can these two things be related? Is there any chance ath9k can loose
some received control packets or 'forget' to send them?

  Thanks.

2011/2/2 Nikolay Martynov <mar.kolya@gmail.com>:
> Hi.
>
> ?Installed new patch and do not have intel stuck yet. Although there
> is still 10-15% ping loss. But not new error messages in dmesg/log.
> I'll keep testing.
>
> ?Two updates:
>
> ?1) last problem I mentioned in previous letter seems to be caused by
> swcrypt=1 on intel side. I just turned it on yesterday and didn't
> realize it can cause such issues. But now I turned it off and it seems
> to be fine.
> ?2) in router logs there are often messages about inability of driver
> to stop rx or tx dma, I'm not sure whether this is relevant or not.
>
> Thanks.
> Nikolay.
>
> 2011/2/2 Felix Fietkau <nbd@openwrt.org>:
>> Please copy the patch from http://nbd.name/560-ath9k_xmit_debug.patch
>> into package/mac80211/patches/ in your OpenWrt build tree.
>>
>> Then recompile and update the ath9k package on your AP and see if it
>> prints the "Aggregation session blocked..." messages when tx to the
>> Intel client stops working.
>>
>> Thanks,
>>
>> - Felix
>>
>> On 2011-02-03 2:46 AM, Nikolay Martynov wrote:
>>> Hi.
>>>
>>> ? I basically have three types of issues:
>>>
>>> ?1) Almost no usable 'n' mode. It is somewhat usable if there is one
>>> client on AP (and I guess relative silence in the air). If there are
>>> two clients intel card becomes unusable - it seems to receive almost
>>> no packets. Mac clients seems to work fine with same AP (didn't try
>>> too long though).
>>>
>>> ? 2) I often get disconnected from AP with message like: wlan1:
>>> deauthenticating from xx:xx:xx:xx:xx:xx by local choice (reason=3).
>>> This happens for no apparent reason, in 'g' mode (and probably 'n'
>>> too, I just do not run 'n' long enough). And this happens with macbook
>>> too. I'm not sure that message is always the same - often there is no
>>> disconnection message. When client tries to connect back there are
>>> different types of timeouts:
>>> ? ?a) on the client (intel):
>>> [78513.691609] wlan1: direct probe to xx:xx:xx:xx:xx:xx (try 1/3)
>>> [78513.888104] wlan1: direct probe to xx:xx:xx:xx:xx:xx (try 2/3)
>>> [78514.088111] wlan1: direct probe to xx:xx:xx:xx:xx:xx (try 3/3)
>>> [78514.288065] wlan1: direct probe to xx:xx:xx:xx:xx:xx timed out
>>> ? ?b) on the client (intel):
>>> [78471.324221] wlan1: associate with xx:xx:xx:xx:xx:xx (try 1)
>>> [78471.524074] wlan1: associate with xx:xx:xx:xx:xx:xx (try 2)
>>> [78471.724064] wlan1: associate with xx:xx:xx:xx:xx:xx (try 3)
>>> [78471.924055] wlan1: association with xx:xx:xx:xx:xx:xx timed out
>>> ? a) and b) happen on intel. I often see 'timeout' in similar mac UI,
>>> but I do not know how to get any diagnostics from mac.
>>> ? At the same time on AP:
>>> ? ?b) hostapd: wlan0: STA xx:xx:xx:xx:xx:xx WPA: EAPOL-Key timeout
>>> ? ?c) hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: did not
>>> acknowledge association response
>>> ? ?b) and c) happen for both intel and mac clients. Moreover - one
>>> client may keep trying to connect while other stays connected and
>>> works fine. But if other disconnects it has problems connecting too.
>>> Problem usually can be fixed by restarting 'wifi' on router. I do not
>>> really know whether this is a ath9k problem, or some hostapd issue.
>>> This may happen several times an hour, but sometimes doesn't happen
>>> for hours. 'Disconnection' part happens more often on intel client.
>>>
>>> ? 3) Intel seems to loose heavy loaded tcp connection sometimes. I.e.
>>> I upload something from laptop to machine connected by wire on the
>>> same router and at some point upload stops and connection timeouts.
>>> Or, if a type a lot of stuff in SSH session - ssh session locks. Looks
>>> like bunch of packets get lost and tcp cannot recover. This happens in
>>> 'g' mode. Often enough so I cannot upload 600Mb file without loosing
>>> connection. Mac doesn't seem to have this problem.
>>>
>>> ? I have TEW-326BRP with trunk openwrt (kernel 2.6.37).
>>> ? On the client - dell laptop with intel5300, to which I have only two
>>> antennas connected - I replaced card from non-'n' and laptop has only
>>> two antennas. OS - ubuntu, 2.6.38 kernel from it's repository + latest
>>> compat wireless + exp ucode + patch from
>>> http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2214.
>>> ? Another client - macbook pro.
>>> ? I think I'm about 30 meters from AP - AP is no second floor and I'm
>>> in the basement (basement has concrete walls - this might affect
>>> signal quality I guess).
>>>
>>> ? It'd be really great to have reliable wifi, so I can devote time and
>>> do whatever testing required.
>>> ? Please let me know how I can help.
>>> ? Thanks!
>>
>
>
>
> --
> Truthfully yours,
> Martynov Nikolay.
> Email: mar.kolya at gmail.com
> Phone: +16478220537
>



-- 
Truthfully yours,
Martynov Nikolay.
Email: mar.kolya at gmail.com
Phone: +16478220537

  reply	other threads:[~2011-02-03  4:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02  5:48 [ath9k-devel] Weird error messages in logs Nikolay Martynov
2011-02-02  5:57 ` Mohammed Shafi
2011-02-02  6:55   ` Ben Greear
2011-02-02  7:01     ` Nikolay Martynov
2011-02-02  7:06       ` Ben Greear
     [not found]         ` <AANLkTik6kJkMEvkCvGSfDDjpYr005DHPwPWp5cACTE+X@mail.gmail.com>
     [not found]           ` <4D499243.9070906@candelatech.com>
     [not found]             ` <AANLkTikF9AhXL5Cj-VHFuszZQ3QgcJ8USXN6CSOGWvn5@mail.gmail.com>
2011-02-02 22:06               ` [ath9k-devel] Fwd: " Nikolay Martynov
2011-02-02 14:24       ` [ath9k-devel] " Felix Fietkau
2011-02-02 14:48         ` Mohammed Shafi
2011-02-02 14:51         ` Mohammed Shafi
2011-02-02 15:13           ` Nikolay Martynov
2011-02-02 15:24             ` Mohammed Shafi
2011-02-02 15:46               ` Felix Fietkau
2011-02-02 23:56                 ` Nikolay Martynov
2011-02-03  0:02                   ` Felix Fietkau
2011-02-03  1:46                     ` Nikolay Martynov
2011-02-03  2:13                       ` Felix Fietkau
2011-02-03  3:16                         ` Nikolay Martynov
2011-02-03  4:50                           ` Nikolay Martynov [this message]
2011-02-03  5:18                             ` Nikolay Martynov
2011-02-07  2:39                               ` Nikolay Martynov
2011-02-07  3:31                                 ` Felix Fietkau
2011-02-03  5:22                 ` Mohammed Shafi
2011-02-02  7:41     ` Mohammed Shafi
2011-02-02  6:04 ` Mohammed Shafi

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=AANLkTik90s0FZbg1x_WhJ7h7kbWU7KsdY56rcdWEPL1z@mail.gmail.com \
    --to=mar.kolya@gmail.com \
    --cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.