Won't connect to wifi unless power_save is disabled

[Vadim Peretokin]

I can connect to most WiFi networks fine, however for one particular WPA/WPA2, EAP-PEAP, MSCHAPV2 network I have to do "sudo iw wlp1s0 set power_save off" before it is able to connect.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-35-generic 4.10.0-35.39
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0c: vadi 4472 F...m pulseaudio
 /dev/snd/pcmC0D0p: vadi 4472 F...m pulseaudio
 /dev/snd/controlC0: vadi 4472 F.... pulseaudio
CurrentDesktop: Unity:Unity7
Date: Thu Sep 28 10:09:15 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8c0e25d4-6e36-428e-b354-4c71b99db752
InstallationDate: Installed on 2017-02-15 (224 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0a5c:5805 Broadcom Corp.
 Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E7470
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-35-generic N/A
 linux-backports-modules-4.10.0-35-generic N/A
 linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-05-24 (126 days ago)
dmi.bios.date: 06/02/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.16.4
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.16.4:bd06/02/2017:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7470
dmi.sys.vendor: Dell Inc.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc2/

[Vadim Peretokin (vperetokin)]

"First, if one is using select proprietary or out-of-tree modules (ex.
vitualbox, nvidia, fglrx, bcmwl, etc.) unless there is an *extra* package
available for the version you are testing, you will need to uninstall the
module first, in order to test the mainline kernel."

I'm using Virtualbox, but the instructions don't say how to uninstall a
module.

On Thu, Sep 28, 2017 at 4:31 PM Joseph Salisbury <
<email address hidden>> wrote:

> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.14 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc2/
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1720092
>
> Title:
> Won't connect to wifi unless power_save is disabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720092/+subscriptions
>

[Vadim Peretokin (vperetokin)]

The issue still persists on a mainline kernel.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]