brcmf_cfg80211_set_pmk() fails with kernel warning on EAP network

Open
#3,783 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, linux

Research direction

Start by reading brcmf_cfg80211_set_pmk() and the same backtrace in issue 3613, then compare the Raspberry Pi kernel behavior with the Ubuntu Server behavior described here. Reproduce the warning on an EAP network using nl80211 rather than the wext workaround; done means the warning no longer occurs in the stated Raspberry Pi setup.

Written by the indexing model from the issue text.

Description

Same backtrace as https://github.com/raspberrypi/linux/issues/3613
See also: https://www.raspberrypi.org/forums/viewtopic.php?t=247310

This is still happening on Linux raspi4 5.4.51-v7l+ #1327 SMP Thu Jul 23 11:04:39 BST 2020 armv7l GNU/Linux so it obviously wasn't resolved. No issue on Ubuntu Server (Linux raspi3 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux).

Adding env wpa_supplicant_driver=wext to the end of /etc/dhcpcd.conf works around the issue by forcing the use of wext instead of nl80211 but this really ought to be fixed the right way.

Building + installing wpa_supplicant 2.9 from source didn't help.

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.