On 12/28/2012 07:07 AM, Linus Torvalds wrote: > Ok, maybe somebody is interested in this.. I don't know what triggered > it, but maybe the few lines around it give some clue. Hi Linus, I am interested (being paid for it kinda helps). The warning itself does not necessarily have to be a problem, but the frameid mismatch between tx status info and the related buffer taken from the DMA ring does. Smells like a race condition, but I need to investigate that. > I think it's new to 3.8-rc1, because I haven't seen it before (well, > I'm running current -git - v3.8.0-rc1-00035-g101e5c7470eb to be exact > - but the networking changes since -rc1 are small and seem unrelated). > But maybe it just happens under certain circumstances. We had a big contribution from Canonical (cc-ed Seth) in brcmsmac itself. Not playing the blame game, but I suspect it has altered circumstances making the real issue (that was already there) more likely to happen. Hope that helps us nailing it down. > Linus > Regards, Arend > --- > [ 573.596631] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp > filtering: enabled true, count 1 (implement) > [ 584.154535] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: > Pkt tx suppressed, illegal channel possibly 1 > [ 584.154628] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: > Pkt tx suppressed, illegal channel possibly 1 > [ 584.925487] ------------[ cut here ]------------ > [ 584.925521] WARNING: at > drivers/net/wireless/brcm80211/brcmsmac/main.c:7539 > brcms_c_wait_for_tx_completion+0xa3/0xc0 [brcmsmac]() -- 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
