From: "Piotr Haber" <phaber@broadcom.com>
To: "David Herrmann" <dh.herrmann@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
"Arend van Spriel" <arend@broadcom.com>,
"John W. Linville" <linville@tuxdriver.com>,
brcm80211-dev-list@broadcom.com, netdev@vger.kernel.org,
"Pieter-Paul Giesberts" <pieterpg@broadcom.com>
Subject: Re: [PATCH regression/bisected] Revert "brcmsmac: support 4313iPA"
Date: Mon, 18 Mar 2013 14:49:57 +0100 [thread overview]
Message-ID: <51471B85.5060404@broadcom.com> (raw)
In-Reply-To: <1363603503-2378-1-git-send-email-dh.herrmann@gmail.com>
On 03/18/13 11:45, David Herrmann wrote:
> This reverts commit b6fc28a158076ca2764edc9a6d1e1402f56e1c0c. It breaks
> wireless AP reconnection on: (14e4:4727)
> Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller
>
> Any attempt to reconnect to an AP results in timeouts no matter how near to the
> AP I am:
> 00:10:40 $nb kernel: wlan0: authenticate with 00:18:39:0a:8e:23
> 00:10:40 $nb kernel: wlan0: direct probe to 00:18:39:0a:8e:23 (try 1/3)
> 00:10:40 $nb kernel: wlan0: direct probe to 00:18:39:0a:8e:23 (try 2/3)
> 00:10:41 $nb kernel: wlan0: direct probe to 00:18:39:0a:8e:23 (try 3/3)
> 00:10:41 $nb kernel: wlan0: authentication with 00:18:39:0a:8e:23 timed out
> ---
> Hi
>
> I tried coming up with a fix instead of reverting this commit, but the commit is
> way to big for me to understand what's going on. Sorry.
>
> With linux-3.8 connecting to an AP broke on my machine. I could connect to an AP
> one time, but any further attempt resulted in:
> 00:10:40 $nb kernel: wlan0: authenticate with 00:18:39:0a:8e:23
> 00:10:40 $nb kernel: wlan0: direct probe to 00:18:39:0a:8e:23 (try 1/3)
> 00:10:40 $nb kernel: wlan0: direct probe to 00:18:39:0a:8e:23 (try 2/3)
> 00:10:41 $nb kernel: wlan0: direct probe to 00:18:39:0a:8e:23 (try 3/3)
> 00:10:41 $nb kernel: wlan0: authentication with 00:18:39:0a:8e:23 timed out
>
> Even sitting right next to the AP didn't help so I started bisecting and it
> turned out to be:
> "brcmsmac: support 4313iPA" b6fc28a158076ca2764edc9a6d1e1402f56e1c0c
> Please revert it.
>
> Thanks
> David
>
Hi,
unfortunately this is not a first report of this patch breaking 4313 for some users.
I'm pretty confident that it is hardware revision related as we have 4313ePA and iPA boards running
successfully in our test setup.
Could you aid us in effort of finding the problem by supplying the contents of this debugfs file:
<debugfs_mount>/brcmsmac/bcma0:0/hardware
Piotr
next prev parent reply other threads:[~2013-03-18 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 10:45 [PATCH regression/bisected] Revert "brcmsmac: support 4313iPA" David Herrmann
2013-03-18 13:49 ` Piotr Haber [this message]
2013-03-18 13:58 ` David Herrmann
2013-03-25 18:58 ` John W. Linville
2013-03-26 9:31 ` Piotr Haber
2013-03-27 14:56 ` John W. Linville
2013-03-27 15:32 ` David Herrmann
2013-03-27 15:43 ` John W. Linville
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=51471B85.5060404@broadcom.com \
--to=phaber@broadcom.com \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=dh.herrmann@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=pieterpg@broadcom.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 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).