From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis R. Rodriguez Date: Wed, 16 Dec 2009 09:41:12 -0800 Subject: [ath9k-devel] Linux bug 14267 "No probe response from AP after 500ms, disconnecting." In-Reply-To: <20091216172356.15849.qmail@stuge.se> References: <20091216172356.15849.qmail@stuge.se> Message-ID: <20091216174112.GD11461@tux> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Wed, Dec 16, 2009 at 09:23:56AM -0800, Peter Stuge wrote: > Is there some more information that I can gather in order to resolve > this issue? Note that disabling power management is not a sufficient > workaround for me, but it makes the error much less frequent. > > http://bugzilla.kernel.org/show_bug.cgi?id=14267#c55 > > #56 has a full debug log of the failure attached. I realize that > stuff going on _before_ the failure is more interesting but to my > untrained eye it looked quite like when things were working ok. > > How often should there be a beacon? Ie. what's the beacon loss timer? That bug report is about issues (so far AR5416 only reported with the PS issue) about disconnections with your AP if PS is left enabled by default which will trigger dynamic PS to be enabled by by default, its all about 2.6.32. The fix on 2.6.32 which should help AR5416 (so far concrete device with issues) is to disable PS by default. You can also disable PS manually if your kernel has it enabled: iwconfig wlan0 power off Your post on that bug report is very different, you say you have merged wireless-testing into your kernel (why??), you also posted a log but it doesn't contain the initailization part of ath9k so your card device cannot be seen. What card is this with? Please keep stable kernel bugs apart from wireless-testing bugs. Wireless-testing is bleedinge edge and as such if you have issues you should use ath9k-devel or the linux-wireless list (like this) and not post on bug reports for stable bugs. Luis