From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Cheng Renquan <crquan@gmail.com>
Cc: "sedat.dilek@gmail.com" <sedat.dilek@gmail.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: linux 3.2-rcX iwlwifi driver's problem (wifi link unstable when moving between multiple APs)
Date: Tue, 10 Jan 2012 14:27:08 -0800 [thread overview]
Message-ID: <1326234428.13074.385.camel@wwguy-huron> (raw)
In-Reply-To: <CAH5vBdKwQ3vPr01PiRMmUqARK4CE44vM9WeVSx-QydpDLQtT1A@mail.gmail.com>
Hi Cheng,
On Tue, 2012-01-10 at 15:17 -0800, Cheng Renquan wrote:
> I've upgraded to Linux 3.2 and roaming failed randomly again,
>
> after the failure it may recover
> sometimes by switch off and on the wifi button on laptop,
> sometimes by "modprobe -r iwlwifi && modprobe iwlwifi",
> sometimes by "stop networkmanager and start networkmanager",
> sometimes recover automatically 10 or 20 minutes later,
> sometimes never recover, infinitely looping (can only move to other
> place, but same place has good wifi coverage verified by other
> colleagues, win/mac users)
>
>
> have checked it has your recent 78feb35 & 81670a4 commits,
> $ git log -n5 --no-merges --oneline v3.2 -- drivers/net/wireless/iwlwifi/
> 96f1f05 iwlwifi: update SCD BC table for all SCD queues
> 78feb35 iwlwifi: allow to switch to HT40 if not associated
> 81670a4 iwlwifi: tx_sync only on PAN context
> 123877b iwlwifi: do not set the sequence control bit is not needed
> 9995ffe iwlwifi: change the default behavior of watchdog timer
>
Are you saying without those two commits (78feb35 & 81670a4), the
roaming works?
Thanks
Wey
next prev parent reply other threads:[~2012-01-10 23:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 23:20 linux 3.2-rcX iwlwifi driver's problem (wifi link unstable when moving between multiple APs) Cheng Renquan
2011-12-20 23:46 ` Guy, Wey-Yi
2011-12-21 2:37 ` Cheng Renquan
2011-12-21 6:22 ` Sedat Dilek
2011-12-21 8:03 ` Cheng Renquan
2011-12-21 8:53 ` Sedat Dilek
2011-12-21 9:06 ` Cheng Renquan
2011-12-21 9:20 ` Sedat Dilek
2011-12-21 10:36 ` Cheng Renquan
2011-12-21 11:14 ` Sedat Dilek
2011-12-21 16:14 ` Guy, Wey-Yi
2011-12-21 23:28 ` Cheng Renquan
2011-12-22 1:40 ` wwguy
2012-01-10 23:17 ` Cheng Renquan
2012-01-10 22:27 ` Guy, Wey-Yi [this message]
2012-01-11 0:01 ` Cheng Renquan
2012-01-10 23:20 ` Guy, Wey-Yi
2012-01-11 1:30 ` Cheng Renquan
2012-01-11 2:28 ` wwguy
2012-01-11 16:37 ` wwguy
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=1326234428.13074.385.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=crquan@gmail.com \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
/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).