On Mon, Oct 24, 2011 at 12:52 AM, Dave Reisner wrote:

On Mon, Oct 24, 2011 at 12:45:04AM -0200, Vitor Eiji Justus Sakaguti wrote:

...

Hi,

Just a heads up to all users of broadcom-wl: a lot of people (myself included) have been reporting kernel panics at boot time after upgrade to current version, so if you're planing to upgrade, be sure to have a live cd around to chroot into your system. There are still no known workarounds other than blacklisting the wl module (thus disabling wireless board) or removing the package.

[1] http://aur.archlinux.org/packages.php?ID=19514

Good luck! Vitor

Or just blacklist the module from the kernel cmdline via "modprobe.blacklist=wl".

Kind of what I said (less verbosely).

It appears to be a race condition that's triggered when its loaded by udev during bootstrap. Loading it afterwards (either from rc.local or manually) doesn't trigger the panic.

It does for me.

No need to freak out.

My point exactly. Cheers

On Mon, Oct 24, 2011 at 2:35 AM, Gaetan Bisson wrote:

[2011-10-24 01:44:50 -0200] Vitor Eiji Justus Sakaguti:

...

On Mon, Oct 24, 2011 at 12:52 AM, Dave Reisner wrote:

...

On Mon, Oct 24, 2011 at 12:45:04AM -0200, Vitor Eiji Justus Sakaguti wrote:

...

Hi,

Just a heads up to all users of broadcom-wl: a lot of people (myself included) have been reporting kernel panics at boot time after upgrade to current version, so if you're planing to upgrade, be sure to have a live cd around to chroot into your system. There are still no known workarounds other than blacklisting the wl module (thus disabling wireless board) or removing the package.

[1] http://aur.archlinux.org/packages.php?ID=19514

Good luck! Vitor

Or just blacklist the module from the kernel cmdline via "modprobe.blacklist=wl".

Kind of what I said (less verbosely).

No. Dave's point is that you don't need a LiveCD: you can just add "modprobe.blacklist=wl" as a parameter to your kernel in the boot loader.

If you look at the comments, you'll see that blacklisting didn't work for hermes14, so I thought other people might run into this problem as well. Better safe than sorry :) But thanks for taking the time to look at this, everyone!