On 02/10/2015 09:01 AM, Ben Greear wrote: > I've hacked CT firmware to do a flush of all vdevs itself when it detects WMI > hang. > I don't have a good test bed to reproduce the problem reliably, but I should > know > after a few days if the flush works at all. If not, then it's a moot point > anyway.
So, this appears to at least partially work. But, what we notice is that when using multiple station vdevs, the system pretty much becomes useless if we get any significant number of stuck or slow-to-transmit management buffers over WMI. Part of this is because WMI messages are sent when holding rtnl much of the time, I think. I would guess that an AP with lots of peers associated might have similar problems if peers are not ACKing packets reliably. Probably the only useful way to fix this is to make the firmware and driver able to send management frames over the normal transport like every other data packet? Any idea what it wasn't written like that to begin with? Thanks, Ben -- Ben Greear <gree...@candelatech.com> Candela Technologies Inc http://www.candelatech.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
