From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Schoenick Date: Fri, 03 Feb 2012 14:37:20 -0800 Subject: BCM4331 fails to associate after suspend In-Reply-To: <20120203222818.GA3749@ubuntu-mba> References: <20120203222818.GA3749@ubuntu-mba> Message-ID: <4F2C61A0.7070802@mozilla.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Seth Forshee Cc: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , Scott Sanbar , linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org On 02/03/2012 02:28 PM, Seth Forshee wrote: > I've been looking into some association problems seen with a MacBook Pro > 8,2 that has BCM4331 wireless, which I've confirmed still exist in > wireless-testing. The association failures reliably start appearing > after the machine is resumed from s3 without external power applied > (whether or not power is applied when the machine is suspended doesn't > matter). > > When the association failures are happening the BCM4331 seems to be able > to receive packets okay, as it can scan successfully. Transmissions > don't work though; no frames from the BCM4331 are ever seen on the air, > as though the tx path is off. Reloading both the b43 and bcma drivers > gets things working again, but reloading just b43 does not. > > I've been looking around a bit in the b43 and bcma drivers, but so far I > haven't found the reason why this happens. Any help would be > appreciated. Let me know if there's additional information I can > provide. > > Thanks, > Seth > > _______________________________________________ > b43-dev mailing list > b43-dev at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/b43-dev I can add that reloading the modules after a suspend/resumes restores functionality, though oddly adding them to SUSPEND_MODULES in pm-utils config does not.