All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: Camaleón <noelamac@gmail.com>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
	664767@bugs.debian.org, linux-wireless@vger.kernel.org,
	"Dan Williams" <dcbw@redhat.com>
Subject: Re: Brcmsmac driver woes, possible regression?
Date: Tue, 19 Mar 2013 22:55:21 +0100	[thread overview]
Message-ID: <5148DEC9.50003@broadcom.com> (raw)
In-Reply-To: <CAKprTDEddPVp+bk7RJX1Jk60b0zVHr4ghvqt0HKnY+h238t3Zw@mail.gmail.com>

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]: <info> (wlan0): supplicant interface state: authenticating -> associating
> Mar 19 17:05:30 stt300 kernel: [26036.586947] wlan0: RX AssocResp from 00:1a:2b:97:7a:97 (capab=0x411 status=0 aid=1)
> Mar 19 17:05:30 stt300 kernel: [26036.587560] brcmsmac bcma0:0: brcmsmac: brcms_ops_bss_info_changed: associated
> Mar 19 17:05:30 stt300 kernel: [26036.587576] brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: true (implement)
> Mar 19 17:05:30 stt300 kernel: [26036.587603] wlan0: associated
> Mar 19 17:05:30 stt300 kernel: [26036.587698] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> Mar 19 17:05:30 stt300 wpa_supplicant[2855]: wlan0: Associated with 00:1a:2b:97:7a:97

Seems to be heading in the right direction, but....

> Mar 19 17:05:30 stt300 NetworkManager[30971]: <info> (wlan0): supplicant interface state: associating -> associated
> Mar 19 17:05:30 stt300 NetworkManager[30971]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
> Mar 19 17:05:32 stt300 avahi-daemon[2630]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::ae81:12ff:fe34:6963.
> Mar 19 17:05:32 stt300 avahi-daemon[2630]: New relevant interface wlan0.IPv6 for mDNS.
> Mar 19 17:05:32 stt300 avahi-daemon[2630]: Registering new address record for fe80::ae81:12ff:fe34:6963 on wlan0.*.
> Mar 19 17:05:32 stt300 NetworkManager[30971]: <warn> Activation (wlan0/wireless): association took too long.

Here it seem to go bad again...

> Mar 19 17:05:32 stt300 NetworkManager[30971]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
> Mar 19 17:05:32 stt300 NetworkManager[30971]: <warn> Activation (wlan0/wireless): asking for new secrets
> Mar 19 17:05:32 stt300 kernel: [26039.005158] wlan0: deauthenticating from 00:1a:2b:97:7a:97 by local choice (reason=3)

And we get a deauth request with WLAN_REASON_DEAUTH_LEAVING.

> Mar 19 17:05:33 stt300 kernel: [26040.004150] brcmsmac bcma0:0: brcmsmac: brcms_ops_bss_info_changed: disassociated
> Mar 19 17:05:33 stt300 kernel: [26040.004172] brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement)
> Mar 19 17:05:34 stt300 kernel: [26040.504402] cfg80211: Calling CRDA to update world regulatory domain
> Mar 19 17:05:34 stt300 ntpd[2611]: Listen normally on 16 wlan0 fe80::ae81:12ff:fe34:6963 UDP 123
> Mar 19 17:05:34 stt300 ntpd[2611]: peers refreshed
> Mar 19 17:05:34 stt300 wpa_supplicant[2855]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
> Mar 19 17:05:34 stt300 NetworkManager[30971]: <info> (wlan0): supplicant interface state: 4-way handshake -> disconnected
> Mar 19 17:05:34 stt300 NetworkManager[30971]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.

I am trying to make sense of it, but it is getting late over here. Have 
a fresh look tomorrow.

Regards,
Arend


  parent reply	other threads:[~2013-03-19 21:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130317144603.GA4850@stt008.linux.site>
     [not found] ` <1363532310.3937.266.camel@deadeye.wl.decadent.org.uk>
     [not found]   ` <20130317152428.GA4940@stt008.linux.site>
     [not found]     ` <1363544257.3937.278.camel@deadeye.wl.decadent.org.uk>
2013-03-17 21:43       ` Bug#703142: compatibility with alx ? Ben Hutchings
2013-03-20  9:07         ` Luis R. Rodriguez
2013-03-20 14:41           ` Ben Hutchings
2013-03-20 15:50             ` Luis R. Rodriguez
2013-03-20 17:45               ` Ben Hutchings
2013-03-26 15:07                 ` Camaleón
     [not found]     ` <20130317175658.GA8181@elie.Belkin>
     [not found]       ` <20130317182725.GA5811@stt008.linux.site>
     [not found]         ` <20130317183344.GA8786@elie.Belkin>
     [not found]           ` <CAKprTDFhNnGOPHUqg8Wn6Cd170KaeXj7-w-D6wS2Cc38vstt5A@mail.gmail.com>
2013-03-18  8:37             ` Brcmsmac driver woes, possible regression? Jonathan Nieder
2013-03-18 19:38               ` Arend van Spriel
2013-03-18 21:14                 ` Camaleón
2013-03-18 21:25                   ` Jonathan Nieder
2013-03-19  9:43                     ` Camaleón
2013-03-19 16:21                       ` Camaleón
2013-03-19 16:53                         ` Dan Williams
2013-03-19 17:30                           ` Camaleón
2013-03-19 17:59                             ` Dan Williams
2013-03-19 18:11                               ` Camaleón
2013-03-19 18:16                                 ` Dan Williams
2013-03-19 18:30                                   ` Camaleón
2013-03-19 21:55                         ` Arend van Spriel [this message]
2013-03-19 22:11                           ` Dan Williams
2013-03-23 15:28                         ` Camaleón
2013-03-24 10:10                           ` Arend van Spriel
2013-03-24 10:37                             ` Camaleón

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=5148DEC9.50003@broadcom.com \
    --to=arend@broadcom.com \
    --cc=664767@bugs.debian.org \
    --cc=dcbw@redhat.com \
    --cc=jrnieder@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=noelamac@gmail.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.