To: =?koi8-r?B?TW9oYW1tZWQgU2hhZmk=?= <shafi.wireless@gmail.com>
From: =?koi8-r?B?TVI=?= <g7af0ec1e3ea1e7b1@nextmail.ru>
CC: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	"=?koi8-r?B?UmFqa3VtYXIgTWFub2hhcmFu?=" <rmanohar@qca.qualcomm.com>
Subject: =?koi8-r?B?UmU6IGF0aDlrIGNyYXNoIDMuMi1yYzc=?=
Date: Tue, 17 Jan 2012 22:53:13 +0400
Message-ID: <NEXT-4f15c399e3e1b1.80658410@nextmail.ru> (sfid-20120117_195331_738768_78354395)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-wireless-owner@vger.kernel.org

 >  > Turned out I got lucky previous time.
 >  > 
 > >This time I went to the other AP, spent some time under it, roamed 
back 
 > and
 >  >
 >  >WiFi didn't disappear. I didn't even lose XMPP connections in the 
 > process.
 >  >
 >  > 
 >  >Maybe debug printing (which prints a lot) managed to introduce some 
 > extra 
 >  > delays into some race condition.
 >  > 
 > > I hope I will have time to test this more on Monday. Tomorrow I will 
be
 >
 >  > using WiFi less than usual.
 > 
 >Now I went a few time back and forth, spent a lot of time under 
previously
 >
 > risky AP and still there are no problems..
 > 
 > I wonder if maybe a congested AP could help.. But unclear how to obtain 
 > that quickly and reliably.
 
Even with debugging off WiFi works reliably across different conditions.