On Fri, 2009-05-08 at 18:23 -0700, Luis R. Rodriguez wrote: > From the looks of it the intel hardware doesn't want to stop the > aggregation session which is API-breakage -- which is why you get the > WARN_ON. Yup. > This is happening when you are disassociating. Exactly. But not always, it seems. > I have a > feeling johill's other patch will fix your issue but regardless I > believe this just highlights more we should flush our queues (both RX > and TX) before scanning. It might fix the disassoc, but I don't think it'll fix this issue. Might make it disappear anyway though. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
