From: Nico Schottelius <nico-linux-20111017@schottelius.org>
To: Arend van Spriel <arend@broadcom.com>
Cc: Nico Schottelius <nico-linux-20111017@schottelius.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BUG: All network processes hang (brcmsmac/wpa_supplicant)
Date: Sun, 23 Oct 2011 12:53:05 +0200 [thread overview]
Message-ID: <20111023105305.GA2489@schottelius.org> (raw)
In-Reply-To: <4EA3E6AD.4030701@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]
Hey Arend,
Arend van Spriel [Sun, Oct 23, 2011 at 12:04:29PM +0200]:
> I see three different AP's in this log. Could you indicate what AP you
> have issues with.
Sure, it's this one:
> [19010.367351] wlan0: RX AssocResp from 00:14:6c:67:9c:32 (capab=0x611
> status=0 aid=2)
> [19010.367355] wlan0: associated
It's a WPNT384 (Netgear), an early pre-draft-n ap.
> With the suspend/resume cycles early in the dmesg log it seems brcmsmac
> gets disassoc/deauth before going to sleep. When things start to get
> flaky this does not seem to happen and I see a lot of deauth reason=2 in
> the log. If I am correct that would mean previousAuthNotValid. Not sure
> why we see that. Will try to reproduce this tomorrow.
Thanks for digging in there. I've to update my report: After another two
suspend/resume cycles, the connection works fine again:
64 bytes from 192.168.42.1: icmp_req=38950 ttl=64 time=103 ms
64 bytes from 192.168.42.1: icmp_req=38951 ttl=64 time=47.4 ms
64 bytes from 192.168.42.1: icmp_req=38952 ttl=64 time=34.1 ms
64 bytes from 192.168.42.1: icmp_req=38953 ttl=64 time=3.57 ms
64 bytes from 192.168.42.1: icmp_req=38954 ttl=64 time=10.6 ms
64 bytes from 192.168.42.1: icmp_req=38955 ttl=64 time=1.24 ms
64 bytes from 192.168.42.1: icmp_req=38956 ttl=64 time=64.8 ms
[...]
I'm watching this problem for the next time and as soon it happens
again, I'll test with other wifi devices to verify that the problem
is not within the AP.
I've attached the updated dmesg.
Cheers,
Nico
--
PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0
[-- Attachment #2: dmesg.gz --]
[-- Type: application/octet-stream, Size: 69222 bytes --]
next prev parent reply other threads:[~2011-10-23 10:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111018111422.GA1979@schottelius.org>
2011-10-18 13:14 ` BUG: All network processes hang (brcmsmac/wpa_supplicant) Arend van Spriel
2011-10-18 13:34 ` Nico Schottelius
[not found] ` <1318940665.2657.60.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
2011-10-19 12:36 ` Nico Schottelius
2011-10-19 12:49 ` Eric Dumazet
2011-10-19 12:58 ` Arend van Spriel
2011-10-19 13:05 ` Eric Dumazet
2011-10-19 13:09 ` Nico Schottelius
2011-10-19 13:07 ` Nico Schottelius
2011-10-19 14:28 ` Nico Schottelius
2011-10-19 14:43 ` Arend van Spriel
2011-10-19 14:55 ` Nico Schottelius
2011-10-19 16:48 ` Arend van Spriel
2011-10-19 21:42 ` Nico Schottelius
2011-10-20 6:28 ` Arend van Spriel
2011-10-22 1:59 ` Nico Schottelius
2011-10-22 8:13 ` Arend Van Spriel
2011-10-22 8:30 ` Greg KH
2011-10-22 8:44 ` Arend van Spriel
2011-10-23 10:04 ` Arend van Spriel
2011-10-23 10:53 ` Nico Schottelius [this message]
2011-10-23 19:48 ` Nico Schottelius
2011-10-24 12:50 ` Arend van Spriel
2011-10-25 6:41 ` Nico Schottelius
2011-10-19 14:46 ` Eric Dumazet
2011-10-19 14:58 ` Nico Schottelius
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=20111023105305.GA2489@schottelius.org \
--to=nico-linux-20111017@schottelius.org \
--cc=arend@broadcom.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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).