From: Seth Forshee <seth.forshee@canonical.com>
To: Arend van Spriel <arend@broadcom.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 09:32:32 -0500 [thread overview]
Message-ID: <20120326143232.GA17126@thinkpad-t410> (raw)
In-Reply-To: <4F7035AD.1080503@broadcom.com>
On Mon, Mar 26, 2012 at 11:23:57AM +0200, Arend van Spriel wrote:
> On 03/24/2012 12:21 PM, Camaleón wrote:
> >2012/3/24 Camaleón<noelamac@gmail.com>:
> >
> >>I will keep and eye on this, bu all seems good and working fine now.
> >
> >Okay, I got another trace :-(
> >
> >NetworkManager asked for the password (which was already set and
> >printed at the input box, I didn't have to type it again) and
> >reconnected fine but it logged the trace at /var/log/messages.
> >
> >See attached files.
> >
>
> 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.
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.
Seth
next prev parent reply other threads:[~2012-03-26 14:32 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 [this message]
2012-03-26 16:54 ` Arend van Spriel
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=20120326143232.GA17126@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=arend@broadcom.com \
--cc=jrnieder@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=noelamac@gmail.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).