From: "John W. Linville" <linville@tuxdriver.com>
To: Nico -telmich- Schottelius <nico-linux-20111118@schottelius.org>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Arend van Spriel <arend@broadcom.com>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
"Rafał Miłecki" <zajec5@gmail.com>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
"Michael Buesch" <m@bues.ch>
Subject: Re: b43: BCM 4331: MacBook 8,1: No connection after suspend
Date: Fri, 18 Nov 2011 14:22:18 -0500 [thread overview]
Message-ID: <20111118192217.GA2663@tuxdriver.com> (raw)
In-Reply-To: <20111118173242.GA2101@schottelius.org>
Arend has nothing to do with b43, and b43 has it's own
mailing list, b43-dev@lists.infradead.org. Even if it didn't,
linux-wireless@vger.kernel.org would be a more appropriate list than
this one.
John
On Fri, Nov 18, 2011 at 06:32:42PM +0100, Nico -telmich- Schottelius wrote:
> Hello,
>
> new notebook, new problems (*):
>
> Running 3.2.0-rc1 on the MacBook Pro 8,1 with the BCM4331
> (14e4:4331) the WLAN indeed works:
>
> [ 86.231702] b43-phy0: Broadcom 4331 WLAN found (core revision 29)
> [ 86.269190] ieee80211 phy0: Selected rate control algorithm
> 'minstrel_ht'
> [ 86.270486] Broadcom 43xx driver loaded [ Features: PMNLS ]
> [ 87.677265] b43-phy0: Loading firmware version 666.2 (2011-02-23
> 01:15:07)
>
> But: After a suspend it seems not to receive any packets anymore:
>
> [ 2334.494845] wlan0: authenticate with 64:87:d7:37:89:89 (try 1)
> [ 2334.694035] wlan0: authenticate with 64:87:d7:37:89:89 (try 2)
> [ 2334.893909] wlan0: authenticate with 64:87:d7:37:89:89 (try 3)
> [ 2335.093824] wlan0: authentication with 64:87:d7:37:89:89 timed out
>
> wpa_supplicant thus retries to connect to the network again and again
> without success.
>
> This is reproducable on the MBP 8,1 and is *NOT* fixed if I unload
> b43 and modprobe it again. It is also "not fixed" when doing
> multiple suspends/resumes.
>
> Any pointers to this?
>
> Cheers,
>
> Nico
>
>
> (*) feels like in good old times...
>
> --
> PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2011-11-18 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 17:32 b43: BCM 4331: MacBook 8,1: No connection after suspend Nico -telmich- Schottelius
2011-11-18 17:39 ` Nico Schottelius
2011-11-18 20:02 ` Arend van Spriel
2011-11-18 20:09 ` Arend van Spriel
[not found] ` <4EC6BB5E.4010101@broadcom.com>
2011-11-18 23:08 ` Rafał Miłecki
2011-11-19 20:02 ` Nico Schottelius
2011-11-19 20:14 ` Rafał Miłecki
2011-11-18 19:22 ` John W. Linville [this message]
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=20111118192217.GA2663@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
--cc=netdev@vger.kernel.org \
--cc=nico-linux-20111118@schottelius.org \
--cc=zajec5@gmail.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).