From: Marcel Holtmann <marcel@holtmann.org>
To: linux-wireless@vger.kernel.org
Subject: Problem with IEEE80211_MONITORING_INTERVAL
Date: Thu, 16 Apr 2009 01:21:12 +0200 [thread overview]
Message-ID: <1239837672.11795.46.camel@violet> (raw)
Hi guys,
so I have an Lenovo X200 with an Intel 5350 cards. This card contains
WiFi and WiMAX radios (not shared). The association with an AP keeps
breaking all the time and it is pretty hard to establish a durable
connection.
After a long debugging session with Reinette we finally tracked down
what is going on here. A full scan with this card takes 7-9 seconds and
that seems to be too long and trigger IEEE80211_MONITORING_INTERVAL
which then deauthenticates us with the AP (reason=6). Problem then is
that the attempt authenticate/associate with the AP fails with all the
time (reason=2). Bringing the interface down/up again doesn't help. It
seems that some internal mac80211 states are messed up. Some times the
whole process stalls completely and nothing happens anymore. Only
unloading and reloading the driver or rebooting helps.
Increasing the IEEE80211_MONITORING_INTERVAL to 10 seconds doesn't
trigger the deauthentication with the AP anymore (or less likely).
During debugging I verified that only the scan actually triggers the
deauthentication. If I don't scan (NM disabled) then everything works
smoothly.
I am running the latest wireless-testing tree (based on 2.6.30-rc2) from
today and the wpa_supplicant from GIT with nl80211 driver.
Regards
Marcel
next reply other threads:[~2009-04-15 23:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 23:21 Marcel Holtmann [this message]
2009-04-16 0:21 ` Problem with IEEE80211_MONITORING_INTERVAL Johannes Berg
2009-04-16 0:44 ` Johannes Berg
2009-04-16 1:12 ` Marcel Holtmann
2009-04-16 1:08 ` Marcel Holtmann
2009-04-16 1:16 ` Johannes Berg
2009-04-16 6:14 ` Kalle Valo
2009-04-16 9:12 ` Johannes Berg
2009-04-16 9:43 ` Johannes Berg
2009-04-16 9:49 ` Kalle Valo
2009-04-16 9:58 ` Johannes Berg
2009-04-16 9:59 ` Kalle Valo
2009-04-16 10:04 ` Johannes Berg
2009-04-16 10:08 ` Kalle Valo
2009-04-16 10:18 ` Johannes Berg
2009-04-16 10:23 ` Kalle Valo
2009-04-16 9:46 ` Johannes Berg
2009-04-20 17:13 ` Marcel Holtmann
2009-04-20 17:20 ` Johannes Berg
2009-04-20 17:26 ` Marcel Holtmann
2009-04-20 17:32 ` Johannes Berg
2009-04-21 19:56 ` Marcel Holtmann
2009-04-21 21:19 ` Johannes Berg
2009-04-22 7:32 ` Marcel Holtmann
2009-04-22 9:03 ` Johannes Berg
2009-04-22 9:12 ` Marcel Holtmann
2009-04-22 9:45 ` Johannes Berg
2009-04-22 11:17 ` Marcel Holtmann
2009-04-22 11:53 ` Marcel Holtmann
2009-04-22 12:14 ` Johannes Berg
2009-04-22 12:56 ` Marcel Holtmann
2009-04-22 13:27 ` John W. Linville
2009-04-22 17:35 ` reinette chatre
2009-04-22 5:04 ` Kalle Valo
2009-04-22 7:27 ` Marcel Holtmann
2009-04-20 18:29 ` Jouni Malinen
2009-04-21 10:47 ` Marcel Holtmann
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=1239837672.11795.46.camel@violet \
--to=marcel@holtmann.org \
--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).