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.
On 09/24/2013 02:52 AM, Michael Stolovitzsky wrote:
> On Mon, Sep 23, 2013 at 10:13:49AM +0200, Arend van Spriel wrote:
>> 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
>>
>
> Arend, much thanks and an apology for not checking the patches. I will try this out ASAP.
>
> Is the (presumedly) low RX gain also a known problem with brcmsmac on BCM4313?
The patch is in 3.12-rc2. There have been more reports on that, but it
still needs to be investigated. Can you provide content of
/sys/kernel/debug/brcmsmac/bcma*/hardware? You need to have
CONFIG_BRCMDBG selected.
Regards,
Arend
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
On 13-09-24, Arend van Spriel wrote:
> On 09/24/2013 02:52 AM, Michael Stolovitzsky wrote:
> >On Mon, Sep 23, 2013 at 10:13:49AM +0200, Arend van Spriel wrote:
> >>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).
> >>>
[...]
> >>
> >>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
> >>
> >
[...]
> The patch is in 3.12-rc2. There have been more reports on that, but
> it still needs to be investigated. Can you provide content of
> /sys/kernel/debug/brcmsmac/bcma*/hardware? You need to have
> CONFIG_BRCMDBG selected.
>
Here you go:
board vendor: 14e4
board type: 587
board revision: 1307
board flags: 402201
board flags2: 884
firmware revision: 262032c
Once again thank you. On 3.12.0-rc2, brcmsmac seems to work fine, which has never happened before, and makes me
very happy. Now I am getting new bug messages that I have to look at.
On Mon, Sep 23, 2013 at 10:13:49AM +0200, Arend van Spriel wrote:
> 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
>
Arend, much thanks and an apology for not checking the patches. I will try this out ASAP.
Is the (presumedly) low RX gain also a known problem with brcmsmac on BCM4313?
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
Same here, using the 3.12.0-rc2 or newer from Ubuntu kernel PPA and my
BCM4313 works flawlessly, something it's never done before. Great
work!
On Wed, Sep 25, 2013 at 1:00 PM, Michael Stolovitzsky
<[email protected]> wrote:
> On 13-09-24, Arend van Spriel wrote:
>> On 09/24/2013 02:52 AM, Michael Stolovitzsky wrote:
>> >On Mon, Sep 23, 2013 at 10:13:49AM +0200, Arend van Spriel wrote:
>> >>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).
>> >>>
> [...]
>> >>
>> >>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
>> >>
>> >
> [...]
>> The patch is in 3.12-rc2. There have been more reports on that, but
>> it still needs to be investigated. Can you provide content of
>> /sys/kernel/debug/brcmsmac/bcma*/hardware? You need to have
>> CONFIG_BRCMDBG selected.
>>
>
> Here you go:
>
> board vendor: 14e4
> board type: 587
> board revision: 1307
> board flags: 402201
> board flags2: 884
> firmware revision: 262032c
>
> Once again thank you. On 3.12.0-rc2, brcmsmac seems to work fine, which has never happened before, and makes me
> very happy. Now I am getting new bug messages that I have to look at.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html