On Tue, 2009-04-28 at 13:38 -0700, John W. Linville wrote: > On Tue, Apr 28, 2009 at 01:39:44PM -0700, reinette chatre wrote: > > On Tue, 2009-04-28 at 10:14 -0700, Valdis.Kletnieks@xxxxxx wrote: > > > On Mon, 27 Apr 2009 15:46:07 PDT, akpm@xxxxxxxxxxxxxxxxxxxx said: > > > > The mm-of-the-moment snapshot 2009-04-27-15-45 has been uploaded to > > > > > > > > http://userweb.kernel.org/~akpm/mmotm/ > > > > > > Saw this while booting at home, out of range of any access points I was > > > configured to associate with (there *are* 4 APs owned by neighbors that I can > > > see via kismet, but wpa_supplicant isn't configured to use them). Didn't > > > happen this morning at my office, when there's APs in range. > > > > > > This didn't happen in mmotm-0424, so it's something new in the last few days. > > > > A recent patch that is related is ... > > > > commit 4583f7455c6b668a4e9cab154b5a7b6c583b288a > > Author: Johannes Berg <johannes@xxxxxxxxxxxxxxxx> > > Date: Thu Apr 23 10:45:04 2009 +0200 > > > > iwlwifi: notify on scan completion even when shutting down > > > > Under certain circumstances iwlwifi can get stuck and will no > > longer accept scan requests, because the core code (cfg80211) > > thinks that it's still processing one. This fixes one of the > > points where it can happen, but I've still seen it (although > > only with my radio-off-when-idle patch). > > > > Signed-off-by: Johannes Berg <johannes@xxxxxxxxxxxxxxxx> > > Acked-by: Reinette Chatre <reinette.chatre@xxxxxxxxx> > > Signed-off-by: John W. Linville <linville@xxxxxxxxxxxxx> > > > > > > Could you please revert this and test again? > > I doubt if that will help -- I just put it into wireless-2.6 and > wireless-testing today. > > > If this does not help, could you please bisect? > > Better bet...unless you meant "apply" instead of "revert"... I did mean revert ... without checking that this patch was in mm yet. Sorry. Reinette -- 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
