Bug#664767: Brcmsmac driver woes, possible regression?

[Camaleón <noelamac@gmail.com>]

2012/3/24 Jonathan Nieder <jrnieder@gmail.com>:

> Camaleón wrote:
>> 2012/3/24 Jonathan Nieder <jrnieder@gmail.com>:
>
>>>                Could you send a summary of the symptoms to
>>> linux-wireless@vger.kernel.org, cc-ing Stanislaw Gruszka
>>> <sgruszka@redhat.com>, Arend van Spriel <arend@broadcom.com>,
>>> and either me or this bug log so we can track it?
> [...]
>> Already done.
>
> Perfect.  Thanks much.

Jonathan,

Although kernel 3.3 still logs the trace (despite having applied all
of the suggested the patches), there's an overall stability
improvement in the wireless driver when compared to kernel 3.2.12
where:

- Wireless link is more prone to connection resets which require for
user interaction to reconnect again
- Reconnects make some running programs to segfault

This snippet comes for kernel 3.2.12 (which I have loaded today with
"brcmsmac.ko" patched) after having experiences one of these
intermittent "reconnects":

Apr  6 19:56:22 stt300 kernel: [32987.534515] gnome-shell[2062]:
segfault at 24 ip b76bbb31 sp bfbf7920 error 4 in
libgnome-shell.so[b7681000+a0000]
Apr  6 19:58:02 stt300 kernel: [33086.718790] mail-notificati[2077]:
segfault at 4c ip 08060063 sp bfe8d4a0 error 4 in
mail-notification[8048000+5c000]

Is there something we can do to improve the driver status in Wheezy? I
can test any pacthes that can make "brcmsmac" to be more stable, at
least to get a stability closer to the one provided by kernel 3.3. I
wouldn't like to see Wheezy users complaining or dropping on the open
source driver and going to "wl" because of this so if there's anything
more I can test, please just tell.

Greetings,

-- 
Camaleón