Comment 29 for bug 732677

Has anyone yet tested Broadcom's recommended workaround for this problem? That is forcefully removing and disabling the stubborn ssb module? See previous comments #17, #14.

Also, reverting to 5.60.* might be a great workaround for this particular bug however the newer driver 5.100.* works well on newer Broadcom chips, so simply reverting 5.100 to 5.60 for all users would seem a little heavy handed.