brcm80211: machine freezing hard with rfkill on

brcm80211: machine freezing hard with rfkill on

[Jiri Slaby]

Hi,

our users report [1] that their machines freeze hard when they have
rfkill turned on and try to run wpa_supplicant or enable network
otherwise. This is with BCM43225 over PCI chip.

Any ideas what that could be or how to fix this?

[1] https://bugzilla.novell.com/show_bug.cgi?id=787649

thanks,
-- 
js
suse labs

Re: brcm80211: machine freezing hard with rfkill on

[Arend van Spriel]

On 07/19/13 09:02, Jiri Slaby wrote:
> Hi,
>
> our users report [1] that their machines freeze hard when they have
> rfkill turned on and try to run wpa_supplicant or enable network
> otherwise. This is with BCM43225 over PCI chip.
>
> Any ideas what that could be or how to fix this?
>
> [1] https://bugzilla.novell.com/show_bug.cgi?id=787649
>
> thanks,

Hi Jiri,

Looking in the bug report it seems to be on 3.4 kernel. The commit below 
is done later.

Regards,
Arend
---------------
commit 82d8eba358badb466a4e988ecabf0668a8d92e9c
Author: Piotr Haber <phaber@broadcom.com>
Date:   Wed Sep 19 22:21:15 2012 +0200

     brcmsmac: don't start device when RfKill is engaged

     This patch fixes a bug when device is being started
     while RfKill switch is engaged, leading to hang
     due to partial initialization of hardware.

     Tested-by: <dragonn@op.pl>
     Reviewed-by: Arend van Spriel <arend@broadcom.com>
     Reviewed-by: Hante Meuleman <meuleman@broadcom.com>
     Signed-off-by: Piotr Haber <phaber@broadcom.com>
     Signed-off-by: Arend van Spriel <arend@broadcom.com>
     Signed-off-by: John W. Linville <linville@tuxdriver.com>

Re: brcm80211: machine freezing hard with rfkill on

[Jiri Slaby]

On 07/19/2013 03:15 PM, Arend van Spriel wrote:
> On 07/19/13 09:02, Jiri Slaby wrote:
>> Hi,
>>
>> our users report [1] that their machines freeze hard when they have
>> rfkill turned on and try to run wpa_supplicant or enable network
>> otherwise. This is with BCM43225 over PCI chip.
>>
>> Any ideas what that could be or how to fix this?
>>
>> [1] https://bugzilla.novell.com/show_bug.cgi?id=787649
>>
>> thanks,
> 
> Hi Jiri,
> 
> Looking in the bug report it seems to be on 3.4 kernel. The commit below
> is done later.

Hi, sorry that I missed this (I thought it was with 3.10) and for the
noise. Thanks for the hint anyway.

-- 
js
suse labs