From: Parag Warudkar <parag.lkml@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
niel.lambrechts@gmail.com
Subject: Re: Probe Timeouts with 47afbaf5af9454a7a1a64591e20cbfcc27ca67a8
Date: Sat, 2 May 2009 07:20:44 -0400 [thread overview]
Message-ID: <f7848160905020420t114db70dq4018bab2ab53fc8f@mail.gmail.com> (raw)
In-Reply-To: <1241252825.13562.20.camel@johannes.local>
On 5/2/09, Johannes Berg <johannes@sipsolutions.net> wrote:
> Parag,
>
>> Just got around to downloading today's compat-wireless and it doesn't
>> work for me - frequent disconnects this time with response timeouts -
>>
>> 9731.902114] wlan1: RX ReassocResp from 00:1e:e5:6a:2c:c2
>> (capab=0x411 status=0 aid=1)
>> [ 9731.902117] wlan1: associated
>> [ 9886.744022] wlan1: no probe response from AP 00:1e:e5:6a:2c:c2 -
>> disassociating
>> [ 9887.594299] wlan1: authenticate with AP 00:1e:e5:6a:2c:c2
>> [ 9887.596953] wlan1: authenticated
>> [ 9887.596958] wlan1: associate with AP 00:1e:e5:6a:2c:c2
>> [ 9887.600997] wlan1: RX ReassocResp from 00:1e:e5:6a:2c:c2
>> (capab=0x411 status=0 aid=1)
>> [ 9887.601000] wlan1: associated
>> [ 9930.640019] wlan1: no probe response from AP 00:1e:e5:6a:2c:c2 -
>> disassociating
>
> This looks like something entirely different.
>
>> Of course mainline continues to work fine after reverting
>> 47afbaf5af9454a7a1a64591e20cbfcc27ca67a8.
>
> Can you make sure the txpower is set correctly, on your compat? Just say
> "iwconfig wlan0" or whatever _while_ associated -- and check that it
> reports 15dBm or so.
It shows 27 dBm when associated - both for mainline and compat.
Still get the disassociated messages.
wlan1 IEEE 802.11bgn ESSID:"pbwloft2"
Mode:Managed Frequency:2.447 GHz Access Point: 00:1E:E5:6A:2C:C2
Bit Rate=1 Mb/s Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:21F9-23AF-AEBB-A427-4ADC-8596-C915-ADC8 [2]
Security mode:open
Power Management:on
Link Quality=38/70 Signal level=-72 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Parag
next prev parent reply other threads:[~2009-05-02 11:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 1:38 Parag Warudkar
2009-05-01 8:16 ` Johannes Berg
2009-05-01 13:19 ` Parag Warudkar
2009-05-11 17:57 ` Linus Torvalds
2009-05-11 18:10 ` Linus Torvalds
2009-05-11 18:22 ` Johannes Berg
2009-05-11 18:33 ` Linus Torvalds
2009-05-11 18:52 ` Johannes Berg
2009-05-11 19:14 ` Linus Torvalds
2009-05-11 20:21 ` Frans Pop
2009-05-01 20:28 ` Parag Warudkar
2009-05-02 8:27 ` Johannes Berg
2009-05-02 11:20 ` Parag Warudkar [this message]
2009-05-02 16:44 ` Johannes Berg
2009-05-02 18:13 ` Parag Warudkar
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=f7848160905020420t114db70dq4018bab2ab53fc8f@mail.gmail.com \
--to=parag.lkml@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=niel.lambrechts@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®