El 2012-05-21 a las 09:07 -0500, Jonathan Nieder escribió: > Camaleón wrote:
> > 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] > > That's no good. It would be nice to get this fixed in 3.2.y upstream > if possible. Just for the record, I've had to stop using brcmsmac for now (it usually went down when doing regular updates in wheezy :-/) and I'm currently running "wl", which runs quite well (no reconnects, no dropdowns and stable as a rock). I'll keep doing tests from time to time when a new kernel arrives (3.4 should be out, so I can compile and test brcmsmac from the mainline, time permitting). > [...] > > Is there something we can do to improve the driver status in Wheezy? > > I think we ought to update brcmsmac to the latest version available > for wheezy. It is a young driver, and the version in 3.2 has serious > problems as described by Seth Forsee[1]: > > | The background is that brcmsmac contains a bunch of code for regulatory > | support that is either duplicated (and in conflict) with the > | protocol-level support or else it would better be handled there. This is > | causing problems on pretty much any channel that isn't part of the > | default world regulatory domain. > | > | I've sent RFC patches that strip out the vast majority of this code in > | favor of better integration with the protocol-level regulatory support. > > Unfortunately that could a little tricky because there might be > changes elsewhere that brcmsmac relies on (bcma, wireless core). > > Jonathan > > [1] > http://thread.gmane.org/gmane.linux.kernel.wireless.general/87873/focus=90727 Thanks for you ongoing support on this, Jonathan. Just "ping" this bug whenever you need I run any specific test, I'll be more than happy to help :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120521175843.ga11...@stt008.linux.site
