This is similar to bug #264683, and the same workaround applies. create the file /etc/pm/config.d/suspend_wl with the contents: SUSPEND_MODULES=wl
This works around the problem, though suspending or removing and then re-inserting the wl module causes my kernel to panic when I try to connect to my campus' unsecured wireless network. Works fine on any secure networks. I will report this bug separately. Is anyone else experiencing kernel panics after suspend/resume when reloading the wl module? This can be tested by: 1. connect to a secured network 2. suspend, and resume in a different location with an unsecured network 3. sudo rmmod wl && sudo modprobe wl - note that the old access points are no longer visible 4. connect to an unsecure network. My kernel panics within 30 seconds. -- [Broadcom wl]: After Resume, NM tries to connect to previous, non-available Wi-Fi network https://bugs.launchpad.net/bugs/452571 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
