From: "George Spelvin" <linux@horizon.com>
To: keescook@chromium.org, linux-crypto@vger.kernel.org
Cc: herbert@gondor.apana.org.au, linux@horizon.com, minipli@googlemail.com
Subject: [BISECTED] 4943ba16 ("include crypto- module prefix") breaks wifi
Date: 16 Feb 2015 22:09:40 -0500 [thread overview]
Message-ID: <20150217030940.7890.qmail@ns.horizon.com> (raw)
I discovered when (belatedly) testing 3.19-rc7 the other week that
my laptop wifi was broken and would no longer associate.
I wasted a lot of time trying to bisect changes in net/wireless and
net/drivers wireless before figuring out that it was sonewhere else in
the kernel. An unrestricted bisect quickly homed in on this commit.
Apparently this is causing some necessary crypto algorithms to fail to
load, breaking my wifi.
Perhaps I'm displaying my ignorance of what's supposed to happen,
but shouldn't make install have installed some files with names like
/lib/modules/`uname r`/kernel/crypto/crypto-*.ko?
Or is it something only I'm hitting because I have a lot of common
crypto algorithms statically compiled into my kernel?
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_586=y
CONFIG_CRYPTO_ARC4=y
In more detail, when things are working, (such as on commit 4943ba1^
= 476c7fe2), wpa_supplicant logs:
wlan1: SME: Trying to authenticate with aa:bb:cc:dd:ee:ff (SSID='FOO' freq=24xx MHz)
wlan1: Trying to associate with aa:bb:cc:dd:ee:ff (SSID='FOO' freq=24xx MHz)
wlan1: Associated with aa:bb:cc:dd:ee:ff
wlan1: WPA: Key negotiation completed with aa:bb:cc:dd:ee:ff [PTK=CCMP GTK=CCMP]
wlan1: CTRL-EVENT-CONNECTED - Connection to aa:bb:cc:dd:ee:ff completed (aith) [id=0 id_str=]
Followed by group rekeying completed messages at 10 minute intervals.
Trying this on kernel 4943ba16 produces instead an endless loop of:
wlan1: SME: Trying to authenticate with aa:bb:cc:dd:ee:ff (SSID='FOO' freq=24xx MHz)
wlan1: Trying to associate with aa:bb:cc:dd:ee:ff (SSID='FOO' freq=24xx MHz)
wlan1: Associated with aa:bb:cc:dd:ee:ff
wlan1: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=aa:bb:cc:dd:ee:ff)
wlan1: CTRL-EVENT-DISCONNECTED bssid=aa:bb:cc:dd:ee:ff reason=1
The kernel logs are not particularly informative.
They just go through the usual successful series, but end with
wlan1: RxAssocResp from aa:bb:cc:dd:ee:ff (capab=0x431 status=0 aid=1)
wlan1: associated
wlan1: deauthenticating from 11:bb:cc:dd:ee:ff by local choice (Reason: 1=UNSPECIFIED)
While successful connection ends before that last line.
next reply other threads:[~2015-02-17 3:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 3:09 George Spelvin [this message]
2015-02-17 6:49 ` [BISECTED] 4943ba16 ("include crypto- module prefix") breaks wifi Mathias Krause
2015-02-17 16:43 ` Kees Cook
2015-02-17 17:47 ` George Spelvin
2015-02-18 6:34 ` George Spelvin
2015-02-18 7:56 ` Mathias Krause
2015-02-25 21:50 ` Kees Cook
2015-04-30 11:00 ` George Spelvin
2015-06-05 23:07 ` Kees Cook
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=20150217030940.7890.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=herbert@gondor.apana.org.au \
--cc=keescook@chromium.org \
--cc=linux-crypto@vger.kernel.org \
--cc=minipli@googlemail.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