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>,
LKML <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: BUG: All network processes hang (brcmsmac/wpa_supplicant)
Date: Wed, 19 Oct 2011 23:42:50 +0200 [thread overview]
Message-ID: <20111019214250.GC2432@schottelius.org> (raw)
In-Reply-To: <4E9EFF51.6000104@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
Arend van Spriel [Wed, Oct 19, 2011 at 06:48:17PM +0200]:
> On 10/19/2011 04:55 PM, Nico Schottelius wrote:
> commit bee709ab1d390afe69e4407bc86bb706c6fb2965
> Merge: ad1c761 1f2c7e9
> Author: Nico Schottelius <nico@kr.ethz.ch>
> Date: Tue Oct 18 00:04:05 2011 +0200
>
> Merge branch 'fix-edp-vdd-power' of ../keithp/linux
>
> As it drops receive packets it may be your problem. Is your AP on 5GHz?
I've to confess I've no clue, but I guess the answer is "some of them":
Here in ETH Zurich (www.ethz.ch) I'm in an environment with a lot of
surrounding APs (probably 7 or more seen with the same ssid).
> From 7d14bd6cbfbf26369c5958e56a468fd8429841d7 Mon Sep 17 00:00:00 2001
> From: Arend van Spriel <arend@broadcom.com>
> Date: Wed, 19 Oct 2011 18:42:45 +0200
> Subject: [PATCH] staging: brcm80211: fix for rate index in receive status
Applied, recompiling, will test tomorrow.
I'll soon (Friday) leave the environment permanently,
thus testing will not be easily possible anymore.
If this issue is 5Ghz related only, can I somehow trigger it without an AP
running in that band / i.e. make the card try to use the 5 Ghz band although
there is no ap nearby?
Cheers,
Nico
--
PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-10-19 21:42 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 [this message]
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
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=20111019214250.GC2432@schottelius.org \
--to=nico-linux-20111017@schottelius.org \
--cc=arend@broadcom.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).