On Mon, Aug 10, 2009 at 11:50 AM, Luis R. Rodriguez<mcgrof@xxxxxxxxx> wrote: > On Mon, Aug 10, 2009 at 8:04 AM, John W. Linville<linville@xxxxxxxxxxxxx> wrote: >> On Sun, Aug 09, 2009 at 10:36:49PM +0200, Rafael J. Wysocki wrote: >>> This message contains a list of some regressions from 2.6.30, for which there >>> are no fixes in the mainline I know of. If any of them have been fixed already, >>> please let me know. >> >> Wireless-related ones... > > Some notes on some of these. > >>> Unresolved regressions >>> ---------------------- >> >>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13947 >>> Subject : Libertas: Association request to the driver failed >>> Submitter : Daniel Mack <daniel@xxxxxxxx> >>> Date : 2009-08-07 19:11 (3 days old) >>> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=57921c312e8cef72ba35a4cfe870b376da0b1b87 >>> References : http://marc.info/?l=linux-kernel&m=124967234311481&w=4 >>> Handled-By : Roel Kluin <roel.kluin@xxxxxxxxx> >>> >>> >>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13943 >>> Subject : WARNING: at net/mac80211/mlme.c:2292 with ath5k >>> Submitter : Fabio Comolli <fabio.comolli@xxxxxxxxx> >>> Date : 2009-08-06 20:15 (4 days old) >>> References : http://marc.info/?l=linux-kernel&m=124958978600600&w=4 > > As I noted earlier this comes from the fact that a driver or mac80211 > is queuing work onto the mac80211 workqueue when we already ran the > mac80211 suspend callbacks and we haven't yet resumed. There have been > several fixes for these, for both drivers and mac80211. We've already > pushed them to wireless-testing but I do not recall which ones have > been propagated to 2.6.31 as fixes. This is on my todo and I haven't looked into this very hard yet, but afaik ath5k doesn't (directly) use the mac80211 workqueue, so my guess in Fabio's case would be further up the stack. -- Bob Copeland %% www.bobcopeland.com -- 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
