On Mon, Sep 22, 2008 at 04:31:33AM -0700, Howard Chu wrote: > Luis R. Rodriguez wrote: > > On Mon, Sep 22, 2008 at 2:09 AM, Howard Chu<hyc@xxxxxxxxx> wrote: > >> > For example - I added DPRINTFs to all the places that called ath9_hw_reset() > >> > to see why the ForceXPAon message was occurring so often, and got the > >> > attached log. I note that ForceXPAon doesn't occur on every call to > >> > hw_reset, and sometimes there are repeated identical calls to set the > >> > channel (e.g. at 22:06:36 in the log). > >> > > >> > It associates successfully with my AP on channel 8, but shortly thereafter > >> > loses the association, scans again, and starts over again, ad nauseam. This > >> > behavior was made even worse when I upgraded my freeradius server (was > >> > authenticating with WPA EAP/PEAP) and configured TLS session caching - there > >> > seems to be a bug in freeradius there so subsequent reassociation attempts > >> > would always fail until I turned off session caching. (Haven't had time to > >> > chase that down yet.) > > > > Howard, did you apply the pending group key patch yet? > > Yes, the patch didn't improve the situation on my wireless-testing build. It > works fine on my 2.6.27-rc6 build though. Can you provide a long of your wireless-testing run with the group key patch applied? Also, please try running wpa_supplicant manually, but first be sure to disable Network Manager completely by doing: # Red Hat based systems sudo /sbin/service NetworkMananger stop # Debian based systems (Ubuntu is one) sudo /etc/init.d/NetworkManager stop sudo killall -TERM wpa_supplicant Please read: http://wireless.kernel.org/en/users/Reporting_bugs Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
