Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver

Bug #1897745 reported by Paul Menzel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

On the Surface Pro 4 with USB Marvell Bluetooth/WLAN device, upgrading from Ubuntu 18.04 with Linux 4.15.x to Ubuntu 20.04 with Linux 5.4.x, only WPA2 Enterprise networks stop working, but other continue to work.

    WPA: Failed to set GTK to the driver (alg=2 keylen=32 keyidx=1)

Starting Ubuntu 20.04.1 with Linux 4.15.x, the problem is gone. Testing Ubuntu’s Linux mainline builds [1], the problem is still there in 5.4.68, but gone in 5.5-rc1.

We do not have the resources to bisect this further, as the user needs the device back now.

[1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/

Revision history for this message
Paul Menzel (paulmenzel) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1897745

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Paul Menzel (paulmenzel) wrote :

The output of `ubuntu-bug` is attached, and contains everything that’s needed as far as I can see.

Revision history for this message
Tom Reynolds (tomreyn) wrote :

Linux version 5.4.0-48-generic (buildd@lcy01-amd64-010) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 (Ubuntu 5.4.0-48.52-generic 5.4.60)
dmesg shows repeat occurrences of:

mwifiex_pcie 0000:02:00.0: crypto keys added
mwifiex_pcie 0000:02:00.0: info: successfully disconnected from [BSSID] reason code 3
mwifiex_pcie 0000:02:00.0: info: trying to associate to 'eduroam' bssid [BSSID]
mwifiex_pcie 0000:02:00.0: info: associated to bssid [BSSID] successfully

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.