On 03/23/2013 04:28 PM, Camaleón wrote:
> 2013/3/19 Camaleón :
>
>>> Now let's see how reverting the patch makes any difference as soon as
>>> I can compile the module. I will keep you updated
>>
>> Update: applied the patch to revert the "other" patch but I still
>> cannot get the driver to work
On Tue, 2013-03-19 at 22:55 +0100, Arend van Spriel wrote:
> On 03/19/2013 05:21 PM, Camaleón wrote:
> > Mar 19 17:05:28 stt300 kernel: [26034.188562] wlan0: authenticated
> > Mar 19 17:05:28 stt300 kernel: [26034.192108] wlan0: associate with
> > 00:1a:2b:97:7a:97 (try 1/3)
> > Mar 19 17:05:28 st
On 03/19/2013 05:21 PM, Camaleón wrote:
Mar 19 17:05:28 stt300 kernel: [26034.188562] wlan0: authenticated
Mar 19 17:05:28 stt300 kernel: [26034.192108] wlan0: associate with
00:1a:2b:97:7a:97 (try 1/3)
Mar 19 17:05:28 stt300 NetworkManager[30971]: (wlan0): supplicant interface
state: authenti
El 2013-03-19 a las 13:16 -0500, Dan Williams escribió:
> On Tue, 2013-03-19 at 19:11 +0100, Camaleón wrote:
(...)
> > > NM minimally verifies the PSK, which by 802.11 standards is between 8
> > > and 63 ASCII characters inclusive. So you should be able to type
> > > anything you want within th
On Tue, 2013-03-19 at 19:11 +0100, Camaleón wrote:
> El 2013-03-19 a las 12:59 -0500, Dan Williams escribió:
>
> > On Tue, 2013-03-19 at 18:30 +0100, Camaleón wrote:
> > > El 2013-03-19 a las 11:53 -0500, Dan Williams escribió:
> > > >
> > > > Note that NM 0.9.8 won't ask for a password when just
El 2013-03-19 a las 12:59 -0500, Dan Williams escribió:
> On Tue, 2013-03-19 at 18:30 +0100, Camaleón wrote:
> > El 2013-03-19 a las 11:53 -0500, Dan Williams escribió:
> > >
> > > Note that NM 0.9.8 won't ask for a password when just anything fails,
> > > but will ask for a password if the 4-way
On Tue, 2013-03-19 at 18:30 +0100, Camaleón wrote:
> El 2013-03-19 a las 11:53 -0500, Dan Williams escribió:
>
> > On Tue, 2013-03-19 at 17:21 +0100, Camaleón wrote:
> > > 2013/3/19 Camaleón :
> > > > 2013/3/18 Jonathan Nieder :
> > > >> Camaleón wrote:
> > > >>> El 2013-03-18 a las 20:38 +0100, A
El 2013-03-19 a las 11:53 -0500, Dan Williams escribió:
> On Tue, 2013-03-19 at 17:21 +0100, Camaleón wrote:
> > 2013/3/19 Camaleón :
> > > 2013/3/18 Jonathan Nieder :
> > >> Camaleón wrote:
> > >>> El 2013-03-18 a las 20:38 +0100, Arend van Spriel escribió:
> > >>
> > Sorry to hear. Reading
On Tue, 2013-03-19 at 17:21 +0100, Camaleón wrote:
> 2013/3/19 Camaleón :
> > 2013/3/18 Jonathan Nieder :
> >> Camaleón wrote:
> >>> El 2013-03-18 a las 20:38 +0100, Arend van Spriel escribió:
> >>
> Sorry to hear. Reading back the bug report I noticed you are having a
> bcm4313 and we re
2013/3/18 Jonathan Nieder :
> Camaleón wrote:
>> El 2013-03-18 a las 20:38 +0100, Arend van Spriel escribió:
>
>>> Sorry to hear. Reading back the bug report I noticed you are having a
>>> bcm4313 and we recently had a regression on it. Could you provide
>>> debugfs information from /brcmsmac/bcma0
Camaleón wrote:
> El 2013-03-18 a las 20:38 +0100, Arend van Spriel escribió:
>> Sorry to hear. Reading back the bug report I noticed you are having a
>> bcm4313 and we recently had a regression on it. Could you provide
>> debugfs information from /brcmsmac/bcma0:0/hardware
>
> I see. My "/sys
El 2013-03-18 a las 20:38 +0100, Arend van Spriel escribió:
> On 03/18/2013 09:37 AM, Jonathan Nieder wrote:
>> Camaleón wrote[1]:
>>
>>> vermagic: 3.9.0-rc2 SMP mod_unload modversions 686
>>>
>>> As soon as I load the brcmsmac module, N-M pop-ups and asks for the
>>> secrets... constantly u
On 03/18/2013 09:37 AM, Jonathan Nieder wrote:
Camaleón wrote[1]:
vermagic: 3.9.0-rc2 SMP mod_unload modversions 686
As soon as I load the brcmsmac module, N-M pop-ups and asks for the
secrets... constantly until it quits, that is, I cannot even connect
to the wifi AP with the Broadcom c
Camaleón wrote[1]:
> vermagic: 3.9.0-rc2 SMP mod_unload modversions 686
>
> As soon as I load the brcmsmac module, N-M pop-ups and asks for the
> secrets... constantly until it quits, that is, I cannot even connect
> to the wifi AP with the Broadcom card, it's a bit frustrating :-(
>
> (atta
El 2012-07-28 a las 13:49 -0500, Jonathan Nieder escribió:
> Camaleón wrote:
> > 2012/7/25 Jonathan Nieder :
>
> >> Hmm. What happens if you try all 23 together again?
> >
> > Compiled today with all the patches and it happens that I get the
> > usual reconnects... I'm completely baffled.
>
> T
Camaleón wrote:
> 2012/7/25 Jonathan Nieder :
>> Hmm. What happens if you try all 23 together again?
>
> Compiled today with all the patches and it happens that I get the
> usual reconnects... I'm completely baffled.
Thanks for the quick feedback. If you don't authenticate with
network-manager
Camaleón wrote:
> 2012/7/23 Jonathan Nieder :
>> Camaleón wrote:
>>> I compiled the kernel today with the 22 patches and today got this:
>>
>> Neat. Ok, we're almost done. Could you try the attached patch (patch
>> 23) without the others against 3.2.y?
>>
>> If it works, I'll submit patches 22 a
Camaleón wrote:
> I compiled the kernel today with the 22 patches and today got this:
Neat. Ok, we're almost done. Could you try the attached patch (patch
23) without the others against 3.2.y?
If it works, I'll submit patches 22 and 23 to stable@ for inclusion
in the 3.2.y tree.
Thanks,
Jonat
Camaleón wrote:
> Sorry for the delay... I've tried kernel 3.2.21 with patches 1 to 19
> but I get random reconnects in just one day:
[...]
> Moreover, if I delay the data input when N-M asks me for the AP
> password, gnome-shell starts segfaulting :-(
Thank you. Next combination to try when you
2012/7/8 Jonathan Nieder :
> Could you try with patches 1-19? (Patches 18, 19, 22, and 23 seem
> potentially interesting.)
Sorry for the delay... I've tried kernel 3.2.21 with patches 1 to 19
but I get random reconnects in just one day:
hpc03@stt300:~$ dmesg | grep -i associated
[ 90.937628]
Camaleón wrote:
> It seems the key patches are from 18 to 23 (remember I'm using ES for
> the regulatory domain) :-?
Yep.
Could you try with patches 1-19? (Patches 18, 19, 22, and 23 seem
potentially interesting.)
Thanks,
Jonathan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.d
2012/7/7 Camaleón :
> A quick follow-up... now running kernel 3.2.21 with the first 17
> patches applied. Let's see how it goes (will comment on the next days)
> and thanks Jonathan for (still!) hanging in there.
I got lots of disconnects today (in only one day using kernel
3.2.21+17 patches), so
2012/7/6 Jonathan Nieder :
> I'll let Arend et al know, and maybe they will have ideas for future
> useful tests. In the meantime, let's brute-force this. :) How does
> 3.2.y + patches 1-17 do?
A quick follow-up... now running kernel 3.2.21 with the first 17
patches applied. Let's see how it go
Camaleón wrote:
> El 2012-06-25 a las 15:13 -0500, Jonathan Nieder escribió:
>> Thanks. Could you try 3.2.21 + all 23 patches again?
>
> Sorry for the delay. I've been running this test (kernel 3.2.21 with
> all the patches applied) since last Saturday which has been running
> quite stable (onl
El 2012-06-25 a las 15:13 -0500, Jonathan Nieder escribió:
> Camaleón wrote:
>
> > I'm afraid I'm getting the old well-known random disconects again
> > (with gnome-shell segfaulting when this happens) ;-(
> >
> > Applied the ten first patches, compiled 3.2.21-1 from Debian sources
> > and... we
Camaleón wrote:
> I'm afraid I'm getting the old well-known random disconects again
> (with gnome-shell segfaulting when this happens) ;-(
>
> Applied the ten first patches, compiled 3.2.21-1 from Debian sources
> and... well, I'm attaching log.
Thanks. Could you try 3.2.21 + all 23 patches agai
Camaleón wrote:
> I'll keep testing brcmsmac with the upstream branch (mainline and
> unstable) so yes, if you have a kernel in your "radar" you think I
> could try just tell and I'll go with it.
Ok, cool. Here's my favorite kernel for the moment:
v3.2.21 + patches 1-10 from http://bugs.debi
El 2012-06-23 a las 12:23 -0500, Jonathan Nieder escribió:
> Camaleón wrote:
> > I noticed there was a new kernel update but as I was centered in this
> > bug report I had configured GRUB to directly boot the older kernel. I'm
> > going to leave the system for a while with the new kernel load
Camaleón wrote:
> El 2012-06-23 a las 12:05 -0500, Jonathan Nieder escribió:
>> Camaleón wrote:
>>> the last (yesterday?) set of updates for
>>> wheezy have left the system in a very bad shape. Is not only that N-M
>>> is reconnecting very often (!) but gnome-shell and mail
El 2012-06-23 a las 12:05 -0500, Jonathan Nieder escribió:
> Camaleón wrote:
>
> > the last (yesterday?) set of updates for
> > wheezy have left the system in a very bad shape. Is not only that N-M
> > is reconnecting very often (!) but gnome-shell and mail-notification
Camaleón wrote:
> the last (yesterday?) set of updates for
> wheezy have left the system in a very bad shape. Is not only that N-M
> is reconnecting very often (!) but gnome-shell and mail-notification
> are segfaulting as crazy horses.
>
> I'm attaching the syslog.
This i
Camaleón wrote:
> Update: I've been running kernel 3.2.2-1 over 4 days (since last
> Saturday until today) and still haven't experienced any disconnection.
Interesting. I wonder if the workaround in f96b08a7e6f6 (brcmsmac:
fix tx queue flush infinite loop, 2012-01-17) has too short a timeout
and
2012/6/11 Camaleón :
> Mmmm, this is something I can still try (an earlier working kernel). As
> per my comment #167 [1], candidates could be lower versions starting
> from "3.2.4-1", which according to the snapshot [2] could be:
>
> 3.2.2-1 (source: linux-2.6 3.2.2-1)
> 3.2.1-2 (source: linux-2.6
El 2012-06-10 a las 17:49 -0500, Jonathan Nieder escribió:
> > This kernel was running fine the whole Saturday but today I had
> > another reconnect (network-manager asked for the password which I had
> > to reconfirm). I'm attaching the full syslog for this pacthed kernel.
> > The reconnect happ
forwarded 664767
http://thread.gmane.org/gmane.linux.kernel.wireless.general/92452
quit
Camaleón wrote:
> I downloaded sid kernel sources for 3.2.19, applied the first of the
> patches ("0001-brcm80211-smac-drop-40MHz-intolerant-flag-from-HT-ca.patch"
> and build a new deb kernel package.
[...]
found 664767 linux-2.6/3.2.19-1
quit
Camaleón wrote:
> Yes. What I get is the Network Manager window requesting for the
> password confirm, randomly. If I delay the password confirmation, the
> wireless connection drops.
[...]
> I downloaded sid kernel sources for 3.2.19, applied the first of the
found 664767 linux-2.6/3.2.18-1
quit
Camaleón wrote:
> I already have that kernel (3.2.18-1) installed and fails.
Marking so. I assume this means it produces the unwanted connection
resets.
Could you try with just the first patch ('drop "40MHz intolerant"
flag') from the series sent before? (
El 2012-06-04 a las 11:42 +0300, Touko Korpela escribió:
> It would be good if you tried Debian kernel 3.2.18-1 (or newer). It has
> "endless retry of A-MPDU transmissions" patch in brcmsmac.
> Maybe it makes some difference.
I already have that kernel (3.2.18-1) installed and fails. I can try
On Sun, Jun 03, 2012 at 02:21:28PM +0200, Camaleón wrote:
> 2012/6/1 Camaleón :
>
> > OTOH, I will try to reproduce the instability state with 3.2.16-1 over
> > the weekend and will comment the results here.
>
> Okay, I'm afraid the problem is still present in kernel 3.2.17-1 :-(
>
> Wireless wa
2012/6/1 Camaleón :
> OTOH, I will try to reproduce the instability state with 3.2.16-1 over
> the weekend and will comment the results here.
Okay, I'm afraid the problem is still present in kernel 3.2.17-1 :-(
Wireless was stable when I tested because I had loaded "wl" driver
instead (I complet
El 2012-06-01 a las 12:42 -0500, Jonathan Nieder escribió:
> Camaleón wrote:
>
> > I'd like to add a comment because I think it can be relevant... since
> > the latest stock kernel update (3.2.18-1) a couple of days ago coming
> > from the usual wheezy set of upgrades (I mean, with no additional
>
Camaleón wrote:
> I'd like to add a comment because I think it can be relevant... since
> the latest stock kernel update (3.2.18-1) a couple of days ago coming
> from the usual wheezy set of upgrades (I mean, with no additional
> patches applied) "brcmsmac" driver seems to run also stable with no
2012/5/30 Jonathan Nieder :
>> Anyway, after having loaded kernel 3.2.19 (with the set of patches
>> applied) for all the weekend and until today, I've experienced NO
>> reconnects nor random connection downs which means the wireless link
>> runs stable and at least it's usable here :-)
>
> Nice.
Ben Hutchings wrote:
> On Wed, 2012-05-30 at 12:27 -0500, Jonathan Nieder wrote:
>> 6b1a89afbf97 brcm80211: smac: drop "40MHz intolerant" flag from HT
>>capability info
>> c261bdf8acad brcm80211: smac: indicate severe problems to Mac80211
>> 0bf1f883fd0a brcm80211: smac: remo
On Wed, 2012-05-30 at 12:27 -0500, Jonathan Nieder wrote:
> found 664767 linux-2.6/3.2.12-1
> tags 664767 - moreinfo
> quit
>
> Camaleón wrote:
>
> > Anyway, after having loaded kernel 3.2.19 (with the set of patches
> > applied) for all the weekend and until today, I've experienced NO
> > reconn
found 664767 linux-2.6/3.2.12-1
tags 664767 - moreinfo
quit
Camaleón wrote:
> Anyway, after having loaded kernel 3.2.19 (with the set of patches
> applied) for all the weekend and until today, I've experienced NO
> reconnects nor random connection downs which means the wireless link
> runs stable
2012/5/27 Jonathan Nieder :
> Thanks. I assume you mean the brcms_c_wait_... warning when you refer
> to an oops. Separating the symptoms:
>
> brcms_c_wait_for_tx_completion warning: bug#672891
> connection resets, segfaults, general instability: bug#664767 (this bug)
> "AMPDU status: BA Time
Hi Camaleón,
Camaleón wrote:
> Mmm... I'm attaching a kernel oops I got after having the module
> loaded, curious is that despite the oops, the wireless link is up and
> running, no reconnects (which reminds me the first reports...). Will
> report back for any other update or change in the wirele
2012/5/26 Camaleón :
> El 2012-05-26 a las 16:07 +0100, Ben Hutchings escribió:
>> In Linux 3.2 you can enable either CONFIG_BCMA (bcma bus driver,
>> supporting the b43 driver) or CONFIG_BRCMSMAC (brcmsmac driver) but not
>> both. Debian has a patch that resolves this conflict, and they are both
El 2012-05-26 a las 16:07 +0100, Ben Hutchings escribió:
> > Any hint? What's the magic line to get brcmsmac back in this kernel
> > version?
>
> I wonder whether you really built from the Debian-patched sources (by
> running debian/bin/test-patches or debian/rules build or similar) or the
> up
On Sat, 2012-05-26 at 16:25 +0200, Camaleón wrote:
> El 2012-05-22 a las 16:18 -0500, Jonathan Nieder escribió:
>
> > Thanks again for your patience. Could you try the attached patch
> > series against a 3.2.18-based kernel (like the one from kernel.org or
> > from sid)?
>
> (...)
>
> Download
El 2012-05-22 a las 16:18 -0500, Jonathan Nieder escribió:
> Thanks again for your patience. Could you try the attached patch
> series against a 3.2.18-based kernel (like the one from kernel.org or
> from sid)?
(...)
Downloaded the sid kernel sources, applied the 23 patches, compiled the
whol
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+a]
> > Apr 6 19:58:02 stt300 kernel: [33086.718790] mail-notif
On Mon, May 21, 2012 at 09:07:51AM -0500, Jonathan Nieder wrote:
>
> Camaleón wrote:
>
> > 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
> >
severity 664767 important
quit
Hi again,
Camaleón wrote:
> 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 p
2012/3/24 Jonathan Nieder :
> Camaleón wrote:
>> 2012/3/24 Jonathan Nieder :
>
>>> Could you send a summary of the symptoms to
>>> linux-wirel...@vger.kernel.org, cc-ing Stanislaw Gruszka
>>> , Arend van Spriel ,
>>> and either me or this bug log so we can track it?
> [...]
>> Alrea
forwarded 664767
http://thread.gmane.org/gmane.linux.kernel.wireless.general/87873
quit
Camaleón wrote:
> 2012/3/24 Jonathan Nieder :
>> Could you send a summary of the symptoms to
>> linux-wirel...@vger.kernel.org, cc-ing Stanislaw Gruszka
>> , Arend van Spriel ,
>> and either me
2012/3/24 Jonathan Nieder :
> Thanks. Nah. Could you send a summary of the symptoms to
> linux-wirel...@vger.kernel.org, cc-ing Stanislaw Gruszka
> , Arend van Spriel ,
> and either me or this bug log so we can track it?
>
> Be sure to mention:
>
> - steps to reproduce the problem, expected res
Camaleón wrote:
> http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.3.tar.bz2
>
> And got another trace
>
> Mar 23 17:50:08 stt300 kernel: [ 112.280060] [ cut here
> ]
> Mar 23 17:50:08 stt300 kernel: [ 112.280123] WARNING: at
> drivers/net/wireless/brcm80211/brcmsmac
2012/3/22 Camaleón :
> I'll compile the latest kernel available from kernel.org this weekend
> and report back as soon as I get useful results.
I just have installed:
http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.3.tar.bz2
And got another trace
Mar 23 17:50:08 stt300 kernel: [ 112.28006
El 2012-03-21 a las 17:00 -0500, Jonathan Nieder escribió:
> Camaleón wrote:
> > 2012/3/21 Camaleón :
>
> >> I'm going to keep the system all the day with wifi connected and see
> >> if I get any trace. Will report back as soon as I can provide the
> >> data. Thanks.
> >
> > I've got another t
Camaleón wrote:
> 2012/3/21 Camaleón :
>> I'm going to keep the system all the day with wifi connected and see
>> if I get any trace. Will report back as soon as I can provide the
>> data. Thanks.
>
> I've got another trace:
[...]
> WARNING: at drivers/net/wireless/brcm80211/brcmsmac/main.c:8234
2012/3/21 Camaleón :
> I'm going to keep the system all the day with wifi connected and see
> if I get any trace. Will report back as soon as I can provide the
> data. Thanks.
I've got another trace:
Mar 21 22:44:07 stt300 kernel: [114985.404111] [ cut here
]
Mar 21 22:44
2012/3/21 Camaleón :
> As instructed in the kernel guide you sent but now the module does not
> compile, once I run:
>
> make drivers/net/wireless/brcm80211/brcmsmac/
>
> Which exists with no errors, there is no "brcmsmac.ko" generated :-?
Okay, I think I finally did it:
root@stt300:/usr/src/lin
2012/3/21 Camaleón :
> Thanks for the detailed steps. The first one looks easier, but this step
> fails:
>
> root@stt300:/usr/src/linux-2.6-3.2.9# fakeroot debian/rules
> setup_i386_none_686-pae
> make: *** No rule to make target `setup_i386_none_686-pae'. Stop.
Okay, some advances. I had to ru
2012/3/21 Jonathan Nieder :
> Possible instructions for building a module to test, based on [1]:
>
> # prerequisites
> apt-get build-dep linux-2.6; # as root
>
> # get and unpack the source
> apt-get source linux-2.6/sid
> cd linux-2.6-
> fakeroot debian/r
Camaleón wrote:
> I know I could try with kernel >3.3-rc2 where the patch is already
> applied
Yep, results from the kernel in experimental would already be interesting.
> but my guess is that you prefer to check if the patch works
> with current kernel 3.2-9 because that's what wheezy
El 2012-03-20 a las 13:36 -0500, Jonathan Nieder escribió:
> Hi Camaleón,
That was fast :-)
> Camaleón wrote:
>
> > Since the last days, I'm experiencing some unstability with the brcmsmac
> > driver
> > and get kernel traces like this in the logs:
> >
> > [ 210.896074] [ cut
Hi Camaleón,
Camaleón wrote:
> Since the last days, I'm experiencing some unstability with the brcmsmac
> driver
> and get kernel traces like this in the logs:
>
> [ 210.896074] [ cut here ]
> [ 210.896138] WARNING: at
> [...]/drivers/net/wireless/brcm80211/brcmsmac/ma
Package: linux-2.6
Version: 3.2.9-1
Severity: normal
Since the last days, I'm experiencing some unstability with the brcmsmac driver
and get kernel traces like this in the logs:
[ 210.896074] [ cut here ]
[ 210.896138] WARNING: at /build/buildd-
linux-2.6_3.2.9-1-i386-YU
70 matches
Mail list logo
