From: "Arend van Spriel" <arend@broadcom.com>
To: "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-rc5]
Date: Thu, 22 Dec 2011 14:19:07 +0100 [thread overview]
Message-ID: <4EF32E4B.7050307@broadcom.com> (raw)
In-Reply-To: <20111222102408.GA2643@schottelius.org>
On 12/22/2011 11:24 AM, Nico Schottelius wrote:
> Update:
>
> - dmesg with hanging logs
> - The hang problem seems to happen ONLY with a specific access point: c8:6c:87:a9:df:a9
> -> this is a zyxel P-2802HWL-I1, running at channel 13, with WPA2-PSK.
> -> If you need more information, just let me know
> - Using wlan with the Samsung S2 as access point seems to work fine
Is the Samsung AP also on channel 13? If not, could you try it?
> So this is now a rather specific issue, but I guess others will run into
> this sooner or later as well.
>
> Attached dmesg with hanging processes including traceback.
>
> Nico
>
Gr. AvS
next prev parent reply other threads:[~2011-12-22 13:19 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
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 ` Arend van Spriel [this message]
2011-12-31 11:48 ` BCM43224 hanging [3.2.0-rc5] 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=4EF32E4B.7050307@broadcom.com \
--to=arend@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico-linux-20111201@schottelius.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.