From: "Arend van Spriel" <arend@broadcom.com>
To: "Michael Stolovitzsky" <emestee@catnarok.net>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list <brcm80211-dev-list@broadcom.com>
Subject: Re: brcmsmac causes soft lockup in 3.12-rc1
Date: Mon, 23 Sep 2013 10:13:49 +0200 [thread overview]
Message-ID: <523FF83D.8030103@broadcom.com> (raw)
In-Reply-To: <20130921223440.GA5297@mail.catnarok.net>
On 09/22/2013 12:34 AM, Michael Stolovitzsky wrote:
> Hi,
>
> On 3.12-rc1, modprobe brcmsmac causes a soft lockup (trace #1), effectively killing the box. This is a Lenovo S206
> with BCM4313 (14e4:4727), which I believe is a bluetooth combo board. After a while,
> RCU scheduler code detects a lockup (trace #2).
>
> This did not happen in 3.11.1, although brcmsmac hasn't worked on this machine
> as far as I remember. In the previous kernels (~3.2.0+), it loads, but the
> reception is extremely weak - you must be within few meters to the AP, and the card would
> die after several minutes. The proprietary wl.ko driver works fine.
>
> I've attached the dmesg output, the kernel configuration and the output of lspci -vnn.
> I'm comfortable with experimenting; please let me know how I can help here.
A fix for this problem has been submitted to John. I think it is in
transit to mainline so probably will be in 3.12-rc2.
Here the URL of the patch:
https://git.kernel.org/cgit/linux/kernel/git/linville/wireless.git/patch/?id=aaa2ced15ad8dca8048666c9f70736424d696a6b
Regards,
Arend
next prev parent reply other threads:[~2013-09-23 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 22:34 brcmsmac causes soft lockup in 3.12-rc1 Michael Stolovitzsky
2013-09-22 5:33 ` Adam Honse
2013-09-22 12:32 ` Michael Stolovitzsky
2013-09-22 17:26 ` Adam Honse
2013-09-23 8:13 ` Arend van Spriel [this message]
2013-09-24 0:52 ` Michael Stolovitzsky
2013-09-24 7:53 ` Arend van Spriel
2013-09-25 18:00 ` Michael Stolovitzsky
2013-09-30 23:32 ` Adam Honse
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=523FF83D.8030103@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=emestee@catnarok.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.