This is still very much a valid issue as of bcmwl-kernel-source 6.30.223.271.
Is there any news/known workaround?
This is still very much a valid issue as of bcmwl-kernel-source 6.30.223.271.
Is there any news/known workaround?