From: Nico Schottelius <nico-linux-20111201@schottelius.org>
To: Arend van Spriel <arend@broadcom.com>
Cc: Nico Schottelius <nico-linux-20111201@schottelius.org>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, b43-dev@lists.infradead.org,
Greg KH <gregkh@suse.de>
Subject: Re: BCM43224 hanging [3.2.0-rc4-00248-gb835c0f]
Date: Fri, 9 Dec 2011 19:00:05 +0100 [thread overview]
Message-ID: <20111209180005.GA5055@ethz.ch> (raw)
In-Reply-To: <4EE0F50B.5040407@broadcom.com>
Hey Arend,
Arend van Spriel [Thu, Dec 08, 2011 at 06:34:03PM +0100]:
> On 12/07/2011 08:08 PM, Nico Schottelius wrote:
> Could you try and see what happens when you kill wpa_supplicant.
I can't kill it, it's in D state :-/
I was just browsing through
drivers/net/wireless/brcm80211/brcmsmac/main.c and it seems that
your patch from my last problem has already been applied.
What may be different this time that the network being used
is *not* on 5Ghz, but 2.4 Ghz (I'm not in the same environment anymore).
Nico
--
PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0
next prev parent reply other threads:[~2011-12-09 18:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 22:48 BCM43224: 00:00:00:00:00:00 address (3.2.0-rc3-00099-g883381d) Nico Schottelius
2011-12-02 11:27 ` Arend van Spriel
2011-12-02 15:01 ` Nico Schottelius
2011-12-07 19:08 ` BCM43224 hanging [3.2.0-rc4-00248-gb835c0f] (was: BCM43224: 00:00:00:00:00:00 address (3.2.0-rc3-00099-g883381d)) Nico Schottelius
2011-12-08 17:34 ` BCM43224 hanging [3.2.0-rc4-00248-gb835c0f] Arend van Spriel
2011-12-09 18:00 ` Nico Schottelius [this message]
2011-12-12 18:16 ` BCM43224 hanging [3.2.0-rc4-00248-gb835c0f] (was: BCM43224: 00:00:00:00:00:00 address (3.2.0-rc3-00099-g883381d)) Nico Schottelius
2011-12-14 11:21 ` BCM43224 hanging [3.2.0-rc5] (was: [3.2.0-rc4-00248-gb835c0f] ...) Nico Schottelius
2011-12-22 10:24 ` Nico Schottelius
2011-12-22 13:19 ` BCM43224 hanging [3.2.0-rc5] Arend van Spriel
2011-12-31 11:48 ` 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=20111209180005.GA5055@ethz.ch \
--to=nico-linux-20111201@schottelius.org \
--cc=arend@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@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 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.