From: "Arend van Spriel" <arend@broadcom.com>
To: "Seth Forshee" <seth.forshee@canonical.com>
Cc: Camaleón <noelamac@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"sgruszka@redhat.com" <sgruszka@redhat.com>,
"jrnieder@gmail.com" <jrnieder@gmail.com>
Subject: Re: brcmsmac still woes, possible regression?
Date: Mon, 26 Mar 2012 18:54:22 +0200 [thread overview]
Message-ID: <4F709F3E.1090405@broadcom.com> (raw)
In-Reply-To: <20120326143232.GA17126@thinkpad-t410>
On 03/26/2012 04:32 PM, Seth Forshee wrote:
> On Mon, Mar 26, 2012 at 11:23:57AM +0200, Arend van Spriel wrote:
>>
>> The WARNING message is preceded by a cfg80211 message regarding
>> world regulatory domain. I suspect there is a relatio, but not sure
>> what it is. Regarding channels 12 and 13 I will come up with a fix
>> today and send you the patch to try.
>
> The trace is related to handling a disconnection, which will also
> trigger a reprocessing of the regulatory rules. The warning and the
> regulatory message share a common cause, but I don't think there's a
> direct relationship between them.
Thanks, Seth
I agree. That seems a more accurate statement. Without additional
tracing (from e.g. wpa_supplicant?) it is hard to say what caused the
disconnect.
> This also seems to indicate that by the time either of these messages
> appears the connection with the AP is already in the process of being
> dropped. I don't think the regulatory messages give any cluse as to why
> the connection was dropped. I suppose the warning might but I don't
> know.
I suspect the warning is caused because mac80211 flush callback is done
after scanning on channels 12 and/or 13. I have a quick fix. The longer
and preferred fix would be to cleanup channel.c and incorporate your
regdom change. I plan to do that in separate patches.
Gr. AvS
next prev parent reply other threads:[~2012-03-26 16:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 8:55 brcmsmac still woes, possible regression? Camaleón
2012-03-24 9:27 ` Arend van Spriel
2012-03-24 10:04 ` Camaleón
2012-03-24 11:21 ` Camaleón
2012-03-26 9:23 ` Arend van Spriel
2012-03-26 9:43 ` Camaleón
2012-03-26 10:10 ` Arend van Spriel
2012-03-26 21:28 ` Camaleón
2012-03-27 8:47 ` Arend van Spriel
2012-03-28 11:19 ` Arend van Spriel
2012-03-28 11:26 ` Camaleón
2012-03-28 12:23 ` Arend van Spriel
2012-03-28 21:59 ` Camaleón
2012-03-29 11:56 ` Arend van Spriel
2012-03-29 13:38 ` Camaleón
2012-04-02 13:29 ` Camaleón
2012-04-02 21:50 ` Jonathan Nieder
2012-04-03 6:25 ` Camaleón
2012-04-03 15:30 ` Arend van Spriel
2012-05-09 9:41 ` Jonathan Nieder
2012-05-09 10:23 ` Arend van Spriel
2012-05-09 10:29 ` Jonathan Nieder
2012-05-09 10:32 ` Arend van Spriel
2012-05-09 17:41 ` Seth Forshee
2012-05-09 18:01 ` Arend van Spriel
2012-05-09 18:10 ` Johannes Berg
2012-05-10 16:35 ` Seth Forshee
2012-05-11 9:32 ` Johannes Berg
2012-05-11 17:31 ` Seth Forshee
2012-05-16 20:15 ` Seth Forshee
2012-05-29 7:16 ` Johannes Berg
2012-03-26 14:32 ` Seth Forshee
2012-03-26 16:54 ` Arend van Spriel [this message]
2012-03-26 17:13 ` Seth Forshee
2012-03-26 17:15 ` 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=4F709F3E.1090405@broadcom.com \
--to=arend@broadcom.com \
--cc=jrnieder@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=noelamac@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.