On Tue, May 18, 2010 at 9:53 AM, Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> wrote: > On Mon, May 17, 2010 at 10:41:40PM -0700, Huub Reuver wrote: >> On Mon, May 17, 2010 at 01:24:04PM -0400, John W. Linville wrote: >> > On Mon, May 17, 2010 at 09:55:31AM -0700, Luis R. Rodriguez wrote: >> > > On Mon, May 17, 2010 at 07:32:41AM -0700, John W. Linville wrote: >> > > > Did you try 2.6.34? I'm pretty sure we merged a fix for this... >> > > >> > > Ditto, and I think it was not related to ath9k but mac80211. >> > > >> > > Was it this maybe? >> > > >> > > commit a9f042cbe5284f34ccff15f3084477e11b39b17b >> > > Author: Ming Lei <tom.leiming@xxxxxxxxx> >> > > Date: Sun Feb 28 00:56:24 2010 +0800 >> > > >> > > ath9k: fix lockdep warning when unloading module >> > > >> > > Johannes had noted: >> > > >> > > "I think the problem is that the locking for sta_notify changed, and a >> > > patch that was written for the new locking was backported to the old, >> > > irq-disabled, locking." >> > >> > Yeah, maybe that is what I was thinking about.... >> >> The traces do not look similar to me, but I'm not a programmer. >> >> I have done a few tests: >> 2.6.32.9 not affected >> 2.6.32.13 affected >> 2.6.33.3 affected >> 2.6.33.4 affected >> 2.6.34 the problem seems to have been fixed. >> >> Sorry for my slow report and response. >> Thanks for your quick answer, I'll have to switch to 2.6.34 for a >> production kernel. > > Eh, I am not sure what happened here... this must've been a fix > regression as I do not recall seeing this on earlier 2.6.32.y releases. > Can you try an earlier 2.6.32.y? I have a fix for this, I'll post this soon, testing 2.6.33 now. 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
