From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: sgruszka@redhat.com, linux@dominikbrodowski.net,
linux-wireless@vger.kernel.org
Subject: Re: 3945ABG fails to connect (3.4-rc1)
Date: Sun, 1 Apr 2012 19:24:08 -0400 [thread overview]
Message-ID: <20120401232407.GA7962@tuxdriver.com> (raw)
In-Reply-To: <20120401.172452.1589857453193260701.davem@davemloft.net>
On Sun, Apr 01, 2012 at 05:24:52PM -0400, David Miller wrote:
> From: Stanislaw Gruszka <sgruszka@redhat.com>
> Date: Sun, 1 Apr 2012 18:52:31 +0200
>
> > On Sun, Apr 01, 2012 at 10:04:19AM +0200, Dominik Brodowski wrote:
> >> Somewhere in between 3.3.0 and 3.4-rc1 my notebook fails to connect to my
> >> local AP:
> >>
> >> 02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
> >>
> >> Snippets from dmesg:
> > [snip]
> >> [ 59.605953] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> >> [ 69.607344] wlan0: disassociating from $INSERT_MAC_HERE by local choice (reason=3)
> >> [ 69.609931] cfg80211: Calling CRDA to update world regulatory domain
> >> [ 69.612438] wlan0: deauthenticating from $INSERT_MAC_HERE by local choice (reason=3)
> > Most likely this is fixed by:
> > http://marc.info/?l=linux-wireless&m=133180823427374&w=2
> >
> > Plese test, thanks.
>
> John, please make sure this gets to me after proper testing.
In fact, you already have it! :-)
commit e92109be7a6a04808c3ed586475ba1e5ea56ecbd
Author: Stanislaw Gruszka <sgruszka@redhat.com>
Date: Thu Mar 15 11:42:49 2012 +0100
iwlegacy: fix BSSID setting
...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-04-02 0:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 8:04 3945ABG fails to connect (3.4-rc1) Dominik Brodowski
2012-04-01 16:52 ` Stanislaw Gruszka
2012-04-01 21:24 ` David Miller
2012-04-01 23:24 ` John W. Linville [this message]
2012-04-02 0:54 ` David Miller
2012-04-05 9:38 ` Dominik Brodowski
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=20120401232407.GA7962@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=sgruszka@redhat.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).