On Mon, May 11, 2009 at 3:06 PM, Pavel Roskin <proski@xxxxxxx> wrote: > On Mon, 2009-05-11 at 00:40 -0700, Luis R. Rodriguez wrote: >> On Sun, May 10, 2009 at 9:17 PM, Pavel Roskin <proski@xxxxxxx> wrote: >> > Quoting "Luis R. Rodriguez" <mcgrof@xxxxxxxxx>: >> > >> >> I can reproduce, and I tried without the idle patches but I still see >> >> the issue. I see this issue only after suspend. Did you suspend and >> >> get this as well? I see this using AR5416. If you are seeing this on >> >> suspend can you try with the patch I posted to linux-wireless to see >> >> if it helps a little? >> > >> > I saw this on AR9280 without any suspends. The card doesn't support the >> > 802.11a range, so it's not a direct equivalent of the problem I bisected >> > with ath5k (invalid rates when scanning and transmitting). >> >> Thanks for the heads up Pavel. So can you guys test with this option >> set as follows: >> >> CONFIG_MAC80211_DEFAULT_PS_VALUE=0 >> >> If using compat-wireless just stuff it into config.mk. >> >> This fixes my issues and points towards PS code. This could be how we >> handle PS in ath9k (more likely) or mac80211. For now please disable >> this if using ath9k until we figure out what causes this. > > It looks like there are two issues, and I confused them. One is > characterized by the kernel messages about the channel, the one > originally reported in this thread. I have seen it, but I don't > remember the exact circumstances. > > Another issue is connection loss to a WPA enabled AP after several > minutes. That's what I have seen with AR9280. iwconfig still shows an > association, but no traffic can flow. > > I just want to tell that it's two different issues. The later is much > more critical for me, but it would take about 15 minutes to verify every > step if bisecting. Unfortunately, I don't have time to bisect it now, > but maybe I'll do it later during this week. Thanks for the heads up, lets address this in another thread then. 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
