From: "Arend van Spriel" <arend@broadcom.com>
To: "Jiri Slaby" <jslaby@suse.cz>
Cc: brcm80211-dev-list@broadcom.com,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Linux kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: brcm80211: machine freezing hard with rfkill on
Date: Fri, 19 Jul 2013 15:15:38 +0200 [thread overview]
Message-ID: <51E93BFA.4090808@broadcom.com> (raw)
In-Reply-To: <51E8E482.30505@suse.cz>
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>
next prev parent reply other threads:[~2013-07-19 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 7:02 brcm80211: machine freezing hard with rfkill on Jiri Slaby
2013-07-19 13:15 ` Arend van Spriel [this message]
2013-07-19 19:31 ` Jiri Slaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51E93BFA.4090808@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).