linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless@vger.kernel.org, Camaleón <noelamac@gmail.com>,
	"Stanislaw Gruszka" <sgruszka@redhat.com>,
	"Seth Forshee" <seth.forshee@canonical.com>,
	"Roland Vossen" <rvossen@broadcom.com>
Subject: Re: [3.2.y] Re: Brcmsmac driver woes, possible regression?
Date: Sun, 29 Jul 2012 17:48:57 -0500	[thread overview]
Message-ID: <20120729224857.GA21285@burratino> (raw)
In-Reply-To: <20120723002808.GA3305@burratino>

Jonathan Nieder wrote:
> Arend van Spriel wrote:

>> I guess the behaviour improved due to the last two patches listed above,
>> but I also suspect that it is only an improvement and the root cause
>> still exists.
>
> I think you're right.  Camaleón tried with all patches except the last
> one and still got the unwanted reconnects.
>
> Would 6b8da423315b and 94a2ca311cf4 be good candidates for stable@ in
> the meantime (for symptom relief and saner regulatory code) until the
> root cause is found?

To answer my own question: I guess not, at least not on the basis of
Camaleón's experience.

Results so far:

 * mainline >= 3.4.y: seemed to be ok for a few days, never showed the
   problem.
 * 3.2.19 + the 23 patches discussed in this thread: worked fine for about
   a week, never showed the problem.
 * 3.2.18: failed quickly.
 * 3.2.19 + first patch: failed quickly.
 * 3.2.2: worked ok for a while, then acted up again.  Affected.
 * 3.2.21 + 10 patches: failed quickly.
 * 3.2.21 + all 23 patches: worked ok-ish (?) for a week ("only a
   couple reconnects in 7 days, but when that happened gnome-shell was
   not segfaulting at least...").  I should have paid more attention:
   that meant it was affected!
 * 3.2.21 + 17 patches: failed quickly.
 * 3.2.21 + 19 patches: failed quickly.
 * 3.2.22 + 22 patches: failed quickly.
 * 3.2.21 + patch #23 alone: failed quickly.
 * 3.2.21 + all 23 patches: failed quickly.

Arend, you're very good at this guessing game. ;-)

I imagine the problem is still present in mainline.  Camaleón, the
next useful test would probably be mainline or wireless-testing, and
we should probably stop being so lazy and try to figure out _what_ is
happening when it reconnects and whether it is even a kernel bug.  It
might be something normal (like rekeying) not being handled well by
userspace.

Whatever it is, it seems that the kernel can help, since the
proprietary Broadcom wl driver works better if I have understood
Camaleón correctly.

Thanks,
Jonathan

  reply	other threads:[~2012-07-29 22:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKprTDFHmBuOorCo4evrYrNEi2-gJov0mQXQpEjoRJicfhWg=A@mail.gmail.com>
     [not found] ` <20120530172713.GH3908@burratino>
     [not found]   ` <CAKprTDGtvUFSBb_XK01bi6bJa3dynu73Lq-jTs=E78E3QwSqpA@mail.gmail.com>
     [not found]     ` <20120601174237.GA31781@burratino>
     [not found]       ` <CAKprTDHepfbCKquvnG8CQ2=-tSNbgOSkT6R0GQmEx9UyuiZyMQ@mail.gmail.com>
     [not found]         ` <CAKprTDHQT8Oodh_YD5CWffSGJXAg-HgFMjR0STVgEZRxH4FaSQ@mail.gmail.com>
     [not found]           ` <20120604084200.GA30645@tiikeri.vuoristo.local>
     [not found]             ` <20120604173121.GA9238@stt008.linux.site>
     [not found]               ` <20120605050620.GC3118@burratino>
     [not found]                 ` <CAKprTDHGqDpdZY4ErZmPEc7Ur81GeQoH8tiAL5hrfhAE0RtbvQ@mail.gmail.com>
2012-06-11  3:15                   ` [3.2.y] Re: Brcmsmac driver woes, possible regression? Jonathan Nieder
2012-06-19 18:15                     ` Jonathan Nieder
2012-06-19 19:15                       ` Arend van Spriel
2012-06-19 19:28                         ` Jonathan Nieder
2012-06-20  7:11                           ` Arend van Spriel
2012-06-20 10:02                             ` Jonathan Nieder
2012-06-20 12:13                               ` Arend van Spriel
2012-06-19 18:51                     ` Arend van Spriel
2012-07-07  4:56                       ` Jonathan Nieder
2012-07-16 21:31                       ` Jonathan Nieder
2012-07-17  7:54                         ` Arend van Spriel
2012-07-23  0:28                           ` Jonathan Nieder
2012-07-29 22:48                             ` Jonathan Nieder [this message]
     [not found]                   ` <20120610224902.GB3419@burratino>
     [not found]                     ` <20120611063014.GA4579@stt008.linux.site>
     [not found]                       ` <CAKprTDHYMyDwvxA52Z9zxP75ZUY5=FfCGPTZZg9ZxTxReFj7pQ@mail.gmail.com>
     [not found]                         ` <20120619180335.GA19354@burratino>
     [not found]                           ` <CAKprTDGM8TJC51Bqideeg447+qR5YnfihgORUFdJL_hW9YHiTw@mail.gmail.com>
2012-06-23 17:50                             ` [3.2.y] " Jonathan Nieder
2012-06-24  9:41                               ` Arend van Spriel

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=20120729224857.GA21285@burratino \
    --to=jrnieder@gmail.com \
    --cc=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=noelamac@gmail.com \
    --cc=rvossen@broadcom.com \
    --cc=seth.forshee@canonical.com \
    --cc=sgruszka@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).