Plugging DisplayPort in L530 causes WiFi disconnection

[Dawid]

I connect running laptop to DisplayPort and wifi is going down (its not sending any packages, however the status is still connected for 2-3 mins).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dawid 1918 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Jul 19 10:38:28 2016
HibernationDevice: RESUME=UUID=2d05849f-f06c-4368-88da-7c7e963ee647
InstallationDate: Installed on 2015-08-10 (343 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 2478CK2
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-31-generic N/A
 linux-backports-modules-4.4.0-31-generic N/A
 linux-firmware 1.157.2
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-25 (85 days ago)
dmi.bios.date: 10/14/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: G3ETA2WW(2.62)
dmi.board.asset.tag: Not Available
dmi.board.name: 2478CK2
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG3ETA2WW(2.62):bd10/14/2014:svnLENOVO:pn2478CK2:pvrThinkPadL530:rvnLENOVO:rn2478CK2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2478CK2
dmi.product.version: ThinkPad L530
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

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.7 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.7-rc7

[Dawid (puradawid)]

This issue started happening after upgrading to 16.04. I have tested v4.7-rc7 kernel and its working okay. Adding tag and marking this bug as confirmed.

[penalvch (penalvch)]

Dawid, the next step is to fully reverse commit bisect from kernel 4.4 to 4.7-rc7 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your help.

[Launchpad Janitor (janitor)]

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