Intel HD Graphics 520 lagging after kernel upgrade

[Frank]

After upgrading to kernel version 4.4.0-53 on a clean install of Lubuntu, I have experienced a persistent problem where the desktop graphics (or any graphics when not using tty 1 to 6) appear to lag or freeze every 1 to 2 seconds for between 0.5 to 1 second. During the freezes, no mouse input is recorded, and most keyboard input is lost.

I'm fairly sure this is a kernel issue, as booting with kernel 4.4.0-31 fixes the issue. This problem is also present in 4.4.0-57.

I am using a Lenovo ThinkPad X1 Carbon with integrated Intel graphics, which aren't the most powerful (they couldn't handle Unity, hence Lubunut). I am running Lubuntu 16.04 LTS, though I have tried a clean install (from the .iso) of Lubuntu 16.10, and this but still appears. The laptop has a4 core i5-6200U processor (2.3 GHz), 8 Gigs of RAM, and Intel HD Graphics 520 (Skylake)

This does not appear to be a thermal issue, or a processor speed issue (the problem persists weather speed step is enabled in the bios or not), though my testing with processor speed step and kernel performance settings (performance/power save) was at best amateur.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-57-generic 4.4.0-57.78
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: david 1078 F.... pulseaudio
CurrentDesktop: LXDE
Date: Wed Dec 21 18:21:04 2016
HibernationDevice: RESUME=UUID=046bb03a-34db-4896-b109-e950967a9fae
InstallationDate: Installed on 2016-12-14 (7 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
MachineType: LENOVO 20FBCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=f802d856-3841-4231-8eb4-80def322e540 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-57-generic N/A
 linux-backports-modules-4.4.0-57-generic N/A
 linux-firmware 1.157.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET43W (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FBCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FBCTO1WW
dmi.product.version: ThinkPad X1 Carbon 4th
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Frank, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

[Frank (frankenpatch)]

Cheers for the reply Christopher

I have tested the mainline version 4.10-rc1 kernel, and unfortunately it did not fix the issue.

I will continue to test as I notice new builds.

I also didn't realise that my bios was outdated. While I'd like to upgrade, would it help this bug to keep my current bios version?

Thanks

[penalvch (penalvch)]

Frank, it's always best for security and bug fixes to keep the BIOS current, as an outdated BIOS can cause various OS related issues, and exposes your computer to security vulnerabilities. For help on updating, please see https://help.ubuntu.com/community/BIOSUpdate .

Once it is updated, please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

[Launchpad Janitor (janitor)]

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