zesty unable to handle kernel NULL pointer dereference

This change was made by a bot.

Do you have a way to reproduce this bug?

If so, would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 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.11-rc6

Unable to reproduce unfortunately. In fact it has not reoccurred, since I filed this bug. Will reopen if it happens again, but I am moving to the more recent released kernel... 4.10.0-15 -> 4.10.0-19.

Not sure what status to mark this bug as until I can get a repro of it.

Speak of the devil... happened again on, will try with upstream kernel.

Linux doe 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Only time I have been able to cause it was high load with lxcs and graphics load (via unity). The mainline does not seem to let my lxd instance load.

Unfortunately my lxd setup does not work with the mainline, [due to snaps/lxd/zfs, one of the above probably](so it will make repro much harder, and stop me from actual work) so I don't think I'll be able to hit it again...

If I can get the above to repro at some later date I will let you know.

This looks like Redhat's bug for this same issue

https://bugzilla.redhat.com/show_bug.cgi?id=1441906

and it refers to an upstream fix

https://bugs.freedesktop.org/show_bug.cgi?id=100516

and also a workaround

https://bugs.freedesktop.org/show_bug.cgi?id=99295#c22

Good find cxreg!

Indeed does look the same, happens when I am running chromium, cxreg found bug happens in Chrome. So some path with the i915 there does appear to be flaky.

Workaround seems to not be super effective given post https://bugs.freedesktop.org/show_bug.cgi?id=99295#c27 unfortunately.

But good to know there is some progress going into the 4.12 queue.

I have this issue and can provide logs if needed. Kernel 4.10.0-20-generic on Zesty. Very, very nasty bug causing very frequent hard crashes. I think the importance ought to be raised on this.

I have implemented the workaround from #7 (https://bugs.freedesktop.org/show_bug.cgi?id=99295#c22) using the attached patchfile on kernel 4.10.0-20.

My system crashed consistently when doing a resource heavy export job on a VirtualBox Windows 10 guest. First try after patching this no longer is the case.

Steps taken to build and install the kernel:

cd /working/directory
apt build-dep linux-image-$(uname -r)
apt source linux-image-$(uname -r)
cd linux-4.10.0/
patch -p1 < /your/patchfile/location/patchfile
debian/rules startnewrelease
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic binary-perarch
cd ..
apt install $PWD/linux-[hit]*21.23*deb

After a few days of using the patched kernel: the patch is not a 100% fix.

So experiencing several crashes a day (hard lock) I decided to install the HWE 4.8 kernel using the Xenial deb files. No more lock ups have occured since.

This seems to me an extremely critical issue at the heart of the OS. I would have expected more visibility on this TBH.

It looks like the patch from Chris Wilson has not landed in mainline yet. However, I'd like to see if this issue still occurs in v4.12-rc1, which is current mainline. If it does, I'll submit the patch upstream for Chris and SRU it to Ubuntu.

The 4.12-rc1 kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/

Just experienced this on kernal 4.10.0-21 while running Chrome (not chromium).

I've experienced apparently random freezes on 17.04 (kernel 4.10.0-21). It appears to happen when Chrome is active, although Chrome is probably active all the time. There's nothing out of the ordinary in kern.log, but syslog has:

May 23 12:44:34 thornback unity-panel-ser[2612]: menus_destroyed: assertion 'IS_WINDOW_MENU(wm)' failed
May 23 12:44:34 thornback compiz[2603]: WARN 2017-05-23 12:44:34 unity.glib.dbus.proxy GLibDBusProxy.cpp:487 Calling method "EmitEvent" on object path: "/com/ubuntu/Upstart" failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.Unity.Test.Upstart was not provided by any .service files
May 23 12:44:34 thornback systemd[2058]: Stopped target A target that, when running, represents the screen being locked.
May 23 12:44:34 thornback systemd[2058]: Stopping Backing Service for the Unity Panel in Lockscreen mode...
May 23 12:44:35 thornback systemd[2058]: Stopped Backing Service for the Unity Panel in Lockscreen mode.
May 23 12:44:37 thornback systemd-resolved[1197]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 192.168.0.254.
May 23 12:44:37 thornback systemd-resolved[1197]: Using degraded feature set (UDP) for DNS server 192.168.0.254.
May 23 12:44:37 thornback compiz[2603]: [4773:4773:0523/124437.777470:ERROR:gpu_child_thread.cc(324)] Exiting GPU process due to errors during initialization

I also notice that there are a number of lines containing:
compiz[2237]: [1:1:0522/101734.457030:ERROR:KeyboardEventManager.cpp(427)] Not implemented reached in static bool blink::KeyboardEventManager::currentCapsLockState()

With Linux XPS13 4.8.0-46-generic:

09:24:36 up 25 days, 10:33, 10 users, load average: 3.49, 2.40, 1.91

4.8.X is super stable, this is on a work laptop with high load.

Every time it has locked up I've been scrolling in chrome.

[28680.993697] CPU: 2 PID: 4930 Comm: chrome Tainted: G OE 4.10.0-20-generic #22-Ubuntu
[28680.993718] Hardware name: Dell Inc. Latitude E7450, BIOS A07 09/01/2015

As an experiment I've disabled hardware acceleration in chrome since all the traces show the drm module (Direct Rendering Module which is in charge of hardware acceleration).

I've been running like this for two weeks with no lockups.

I don't use compiz - I just use plain XFCE so no OpenGL needed for my desktop hopefully.

I have a similar problem, plug the mobil to the usb and the PC frozen:

Kernel: 4.10.0-21-generic

May 29 12:15:37 roal kernel: [13126.330476] usb 2-1: new high-speed USB device number 3 using ehci-pci
May 29 12:15:37 roal kernel: [13126.479378] usb 2-1: New USB device found, idVendor=22b8, idProduct=2e82
May 29 12:15:37 roal kernel: [13126.479391] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 29 12:15:37 roal kernel: [13126.479398] usb 2-1: Product: XT1562
May 29 12:15:37 roal kernel: [13126.479403] usb 2-1: Manufacturer: motorola
May 29 12:15:37 roal kernel: [13126.479408] usb 2-1: SerialNumber: Z***MZ
May 29 12:15:37 roal kernel: [13126.546640] [UFW BLOCK] IN=enp0s10 OUT= MAC= SRC=fe80:0000:0000:0000:1a54:8c81:4366:67ff DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=338319 PROTO=UDP SPT=8612 DPT=8612 LEN=24
May 29 12:15:37 roal kernel: [13126.546657] [UFW BLOCK] IN=enp0s10 OUT= MAC= SRC=fe80:0000:0000:0000:1a54:8c81:4366:67ff DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=185378 PROTO=UDP SPT=8612 DPT=8610 LEN=24
May 29 12:15:37 roal kernel: [13126.556808] [UFW BLOCK] IN=enp0s10 OUT= MAC= SRC=fe80:0000:0000:0000:1a54:8c81:4366:67ff DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=338319 PROTO=UDP SPT=8612 DPT=8612 LEN=24
May 29 12:15:37 roal kernel: [13126.556826] [UFW BLOCK] IN=enp0s10 OUT= MAC= SRC=fe80:0000:0000:0000:1a54:8c81:4366:67ff DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=185378 PROTO=UDP SPT=8612 DPT=8610 LEN=24
May 29 12:19:23 roal kernel: [13352.534728] BUG: unable to handle kernel NULL pointer dereference at 0000000000000020
May 29 12:19:23 roal kernel: [13352.535958] IP: dma_fence_wait_timeout+0x36/0xf0
May 29 12:19:23 roal kernel: [13352.537127] PGD 0
May 29 12:19:23 roal kernel: [13352.537129]
May 29 12:19:23 roal kernel: [13352.539448] Oops: 0000 [#3] SMP
May 29 12:19:23 roal kernel: [13352.540617] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cmac bnep snd_hda_codec_hdmi binfmt_misc snd_hda_codec_via snd_hda_codec_generic input_leds btusb btrtl btbcm btintel bluetooth edac_mce_amd edac_core kvm_amd kvm snd_hda_intel snd_hda_codec k10temp snd_hda_core snd_hwdep snd_pcm irqbypass serio_raw snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq shpchp snd_seq_device snd_timer snd soundcore i2c_nforce2 asus_atk0110 mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast parport_pc nf_nat_ftp ppdev nf_nat
May 29 12:19:23 roal kernel: [13352.545655] libcrc32c nf_conntrack_ftp nf_conntrack lp iptable_filter parport ip_tables x_tables autofs4 hid_generic usbhid hid pata_acpi nouveau mxm_wmi i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse forcedeth ahci libahci pata_amd video fjes wmi

Can folks affected by this bug please test the v4.12-rc3 kernel? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3

I'm running on a custom kernel since this bug occurred to me a few weeks ago. This was actually before the first rc (next branch) I'm therfore not 100% sure if it got merged or not. I will build a new kernel 12 RC tomorrow and report back (I can't use the upstream ppa versions as it lacks aufs).

I need zfs and it fails on the proprietary nvidia driver too. I'll see if I can get it running.

@Joseph,

I just tried and my Dell XPS 13 9343 does not boot (hangs with a blank screen right after kernel selection in grub) with generic variants from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2017-05-31/
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2017-05-30/

Same system boots fine with generic variants from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2017-05-23/
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2017-05-27/

Same issue with generic variant from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2017-06-01/ this morning.

Also tried to select recovery mode in grub, no better: I only get a black console screen with a blinking cursor in the upper left.

No error message, nothing in the logs.

FWIW, here's the very beginning of dmesg with zesty's standard kernel:

```
[ 0.000000] Linux version 4.10.0-22-generic (buildd@lcy01-08) (gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) ) #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 (Ubuntu 4.10.0-22.24-generic 4.10.15)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=UUID=5f1b119b-2beb-4d5b-aabf-606390f6d767 ro
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000c367efff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000c367f000-0x00000000dae91fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000dae92000-0x00000000daebbfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000daebc000-0x00000000db7f3fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000db7f4000-0x00000000dbafefff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000dd000000-0x00000000df7fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x0...

v4.12-rc3 works for me, had it in the last 3 days, no crash. Dell XPS 13 9350 ...

> I just tried and my Dell XPS 13 9343 does not boot (hangs with a blank screen right after kernel selection in grub) with generic variants from:
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3

I can replicate this. Dell Latitude E7250.

For those like me that fail booting 4.12rc3 but had no issue with previous builds, this looks like a interesting trail: https://bugs.launchpad.net/linux/+bug/1694561

Having this issue with Asus UX303UB, kernel 4.11.3 64 bits, Ubuntu 16.04.
Might be related to [this systemd kbus bug](https://github.com/systemd/systemd/issues/378).

Dell XPS 13 9343 running fine with https://patchwork.freedesktop.org/patch/158340/ applied on top of Ubuntu-4.10.0-22.24.

Got the hint from https://bugs.freedesktop.org/show_bug.cgi?id=99295#c53

I'm experiencing the same issue for a while now. I think it occurred after I upgraded form Yakkety to Zesty.

I'm currently on 4.10.0-21-generic.

I think the issue is more likely to happen when I run CPU and / or RAM intensive applications.

If this happens, all my screens are stuck.

has this been backported to 4.10 yet?

so far so go 4.10.0-22-generic is. maybe because I stopped using chrome and use firefox instead?

2 days uptime and no crash

I'm running 4.10.0-22-generic and it is still crashing (at least 2 to 5 times a day) (not only when running chrome, a couple of other applications also cause this kernel panic to happen which completely makes ubuntu (and any other linux distro on 4.10/4.11) unusable for work @the moment...

I hope somebody can/will fix(/backport) this soon since I might have to resort to using OSX or Windows to actually get some work done :( (and a blame to the freedesktop kernel dev's for not backporting this asap into mainline, this affects almost every user on 4.10/4.11 kernels and should be fixed upstream)

just install 4.8-X from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.17/

but yeah I agree this should have been fix long time ago. there is even a backport for 4.10 this has to go into the ubuntu kernel

what takes so much time i donno

This is relatively hard to reproduce. It happens sometimes directly after boot and login, sometimes after more than a week uptime.

I've simply selected an older kernel at boot (4.8.0-46-generic; the newest one I had installed from Yakkety) and I didn't experience a crash, yet.

I am having this issue on Xubuntu Xenial with the linux-generic-hwe-16.04-edge kernel. It happened once a long time ago, but now it is happening again. This bug happens when the system is under load and more graphical load is demanded. On my specific case, when my system is already under some load and then I open a software which demands both high video memory (shared memory) and RAM memory, as games can do, then the system freezes.

I can see the memory usage increase while the software is loading, until the system completely freezes. To reboot, the two options are a hard reset or SysRq keys.

My computer is a Lenovo Ideapad 310, with a Intel Core i3-6100U, with a Intel HD Graphics 520 graphical chip. It has 4 GB of RAM and, when the bug happens, there is always heavy RAM usage. This bug never happened to me without high RAM usage.

This bug is not easy to reproduce, but with some tries while the system is under load it is possible to freeze the system.

Here is my log. I was watching a video on YouTube while I was chatting in Discord, with Steam opened and was loading the game Robocraft. Basically, heavy load. As the Robocraft loaded, it required both RAM and video memory, which weren't plentiful due to the other software's usage. Then it crashed.

Jun 9 22:00:54 usuario-Lenovo-ideapad-310-14ISK kernel: [16404.020383] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
Jun 9 22:00:54 usuario-Lenovo-ideapad-310-14ISK kernel: [16404.020455] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x124/0x270 [i915]
Jun 9 22:00:54 usuario-Lenovo-ideapad-310-14ISK kernel: [16404.021756] PGD 1649d2067
Jun 9 22:00:54 usuario-Lenovo-ideapad-310-14ISK kernel: [16404.021757] PUD 16c731067
Jun 9 22:00:54 usuario-Lenovo-ideapad-310-14ISK kernel: [16404.023034] PMD 0
Jun 9 22:00:54 usuario-Lenovo-ideapad-310-14ISK kernel: [16404.024842]
Jun 9 22:00:54 usuario-Lenovo-ideapad-310-14ISK kernel: [16404.026857] Oops: 0002 [#1] SMP
Jun 9 22:00:54 usuario-Lenovo-ideapad-310-14ISK kernel: [16404.027842] Modules linked in: ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 bridge stp llc ebtable_filter ebtables rfcomm bnep binfmt_misc nls_iso8859_1 arc4 rtsx_usb_ms memstick uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_sst_match snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_pcm snd_seq_midi snd_seq_midi_event aesni_intel ath10k_pci ath10k_core aes_x86_64 crypto_simd glue_helper ath cryptd
Jun 9 22:00:54 usuario-Lenovo-ideapad-310-14ISK kernel: [16404.033493] snd_rawmidi mac80211 intel_cstate snd_seq snd_seq_device intel_rapl_perf snd_timer cfg80211 joydev input_leds snd serio_raw soundcore shpchp mei_me mei btusb intel_pch_thermal btrtl ucsi hci_uart btbcm btqca ideapad_laptop btintel sparse_keymap bluetooth kvm_intel kvm acpi_pad mac...

I think I had the same problem on zesty. It started occurring AFTER I used nvidia-settings to switch to integrated intel graphics on a Dell XPS-15 9560 (GTX1050) and completely uninstalled nvidia drivers to get back to a working laptop.

Indeed it seems to happen while using chromium. My machine was nog completely crashed though, I could still ssh into it. But restarting X or even rebooting was impossible, I did need to force power off.

I installed the upstream kernel, to be precise: linux-image-4.12.0-041200rc3-generic_4.12.0-041200rc3.201705282131_amd64.deb

For about a day now the laptop is very stable and VERY cool. No fan noise and battery usage seems to be much better than ever before without nvidia drivers.

Can't wait to get this kernel fully supported.

I have this bug on Dell XPS 13 9360 with Ubuntu 16.04 and 4.10.0-22-generic (installed as depend of linux-generic-hwe-16.04-edge).

Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671314] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671360] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x124/0x270 [i915]
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671378] PGD 46428e067
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671379] PUD 45a436067
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671388] PMD 0
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671396]
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671409] Oops: 0002 [#1] SMP
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671419] Modules linked in: uas usb_storage ccm cmac arc4 nvram msr ath10k_pci ath10k_core ath mac80211 cfg80211 rfcomm cdc_ether usbnet snd_usb_audio snd_usbmidi_lib r8152 mii pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btusb btrtl bnep nls_iso8859_1 hid_multitouch snd_hda_codec_hdmi dell_led i2c_designware_platform i2c_designware_core snd_soc_skl snd_soc_skl_ipc dell_wmi snd_soc_sst_ipc dm_crypt snd_soc_sst_dsp snd_hda_ext_core snd_soc_sst_match snd_hda_codec_realtek snd_soc_core snd_hda_codec_generic dell_laptop dell_smbios dcdbas snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_pcm coretemp
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671593] kvm_intel kvm snd_seq_midi snd_seq_midi_event irqbypass crct10dif_pclmul snd_rawmidi crc32_pclmul ghash_clmulni_intel pcbc snd_seq aesni_intel aes_x86_64 crypto_simd snd_seq_device glue_helper snd_timer cryptd snd input_leds joydev serio_raw soundcore rtsx_pci_ms memstick mei_me idma64 mei virt_dma processor_thermal_device shpchp intel_soc_dts_iosf intel_pch_thermal intel_lpss_pci hci_uart btbcm btqca soc_button_array intel_vbtn btintel intel_hid bluetooth intel_lpss_acpi intel_lpss int3403_thermal tpm_crb mac_hid int340x_thermal_zone int3400_thermal sparse_keymap acpi_thermal_rel acpi_pad acpi_als kfifo_buf industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_logitech_hidpp hid_logitech_dj hid_plantronics usbhid dm_mirror dm_region_hash dm_log rtsx_pci_sdmmc i915
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671768] i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops nvme drm rtsx_pci nvme_core i2c_hid wmi hid video fjes
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671805] CPU: 3 PID: 16658 Comm: skypeforlinux Tainted: G W OE 4.10.0-22-generic #24~16.04.1-Ubuntu
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671830] Hardware name: Dell Inc. XPS 13 9360/0839Y6, BIOS 1.3.5 05/08/2017
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671849] task: ffff9970b4215c00 task.stack: ffffb2f3c5294000
Jun 16 00:55:13 adept-XPS-13-9360 kernel: [155563.671877] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x124/0x270 [i915]
Jun 16 00:55:13 adept-XPS-13-9360 kerne...

Well, the patch I mentioned in comment #28 is not perfect, crashes still happen, just way less often (I achieved several days uptime while without the patch the crashed usually happened twice a day).

Today's crash with the patch on top of Ubuntu-4.10.0-23.25 tag:

Jun 16 12:21:15 patrickxps kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
Jun 16 12:21:15 patrickxps kernel: IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
Jun 16 12:21:15 patrickxps kernel: PGD 0
Jun 16 12:21:15 patrickxps kernel:
Jun 16 12:21:15 patrickxps kernel: Oops: 0002 [#1] SMP
Jun 16 12:21:15 patrickxps kernel: Modules linked in: ccm rfcomm xfrm_user xfrm_algo xt_addrtype br_netfilter overlay xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4
Jun 16 12:21:15 patrickxps kernel: videobuf2_v4l2 input_leds btusb joydev btrtl serio_raw btbcm videobuf2_core btintel bluetooth videodev media dell_led dell_smbios hid_multitouch dcdbas snd_soc_rt298 snd_s
Jun 16 12:21:15 patrickxps kernel: int3400_thermal kfifo_buf mei shpchp intel_soc_dts_iosf int3406_thermal acpi_thermal_rel int340x_thermal_zone intel_hid industrialio sparse_keymap mac_hid intel_smartconne
Jun 16 12:21:15 patrickxps kernel: CPU: 0 PID: 1675 Comm: Xorg Tainted: P W O 4.10.0-23-generic #25
Jun 16 12:21:15 patrickxps kernel: Hardware name: Dell Inc. XPS 13 9343/0310JH, BIOS A12 05/09/2017
Jun 16 12:21:15 patrickxps kernel: task: ffff9ddf0dec1680 task.stack: ffffc18303234000
Jun 16 12:21:15 patrickxps kernel: RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
Jun 16 12:21:15 patrickxps kernel: RSP: 0018:ffffc18303237880 EFLAGS: 00010246
Jun 16 12:21:15 patrickxps kernel: RAX: ffff9dde000c1b40 RBX: 0000000000000003 RCX: 0000000000000003
Jun 16 12:21:15 patrickxps kernel: RDX: 0000000000000000 RSI: ffff9ddf07747000 RDI: ffff9ddf0b3f0000
Jun 16 12:21:15 patrickxps kernel: RBP: ffffc183032378d8 R08: 0000000000000000 R09: 0000000000000000
Jun 16 12:21:15 patrickxps kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff9dde001a2000
Jun 16 12:21:15 patrickxps kernel: R13: ffff9ddea3fb70d0 R14: 00000000fc73e000 R15: 0000000000010000
Jun 16 12:21:15 patrickxps kernel: FS: 00007fabaecbca40(0000) GS:ffff9ddf1f400000(0000) knlGS:0000000000000000
Jun 16 12:21:15 patrickxps kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 16 12:21:15 patrickxps kernel: CR2: 0000000000000018 CR3: 000000020fe66000 CR4: 00000000003406f0
Jun 16 12:21:15 patrickxps kernel: Call Trace:
Jun 16 12:21:15 patrickxps kernel: gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
Jun 16 12:21:15 patrickxps kernel: ? swiotlb_map_sg_attrs+0x49/0x110
Jun 16 12:21:15 patrickxps kernel: gen8_alloc_va_range+0x23d/0x470 [i915]
Jun 16 12:21:15 patrickxps kernel: i915_vma_bind+0x7e/0x170 [i915]
Jun 16 12:21:15 patrickxps kernel: __i915_vma_do_pin+0x2a5/0x450 [i915]
Jun 16 12:21:15 patrickxps kernel: i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
Jun 16 12:21:15 patrickxps kernel: i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
Jun 16 12:21:15 patrickxps kernel: i915_gem_do_execbuffer.isra.38+0x4ca/0x15c0 [i915...

I got the same error - it happens twice:

Kernel: 4.11.5-1-ARCH (upgrading now to 4.11.7, but i will try 4.12 RC)

[881346.853394] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
[881346.853465] IP: gen8_ppgtt_alloc_page_directories.isra.16+0xd9/0x280 [i915]

But it's like once a week, i notice that it only happens (but not always) when i get full memory and it starts to swap (and that's like once a week on 16GB of ram, it gets full because of those electron app that after a while use even 1.5GB/app, so periodically i restart them to maintain low (under 8GB) memory usage.

Before (but probably still) on KDE whenever i got my memory full the plasma will just totally freeze until some app doesn't crash with OOM, but that takes a while until the swap is filled up or i kill some apps from console/ssh.

And other apps (like music playback, ssh) still works after i915 crash.

just had this:
Jul 3 15:06:22 XPS13 kernel: [36225.817104] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
J

i was ok for a week, than opened chrome and boom.

FYI, 4.12 was released as stable yesterday, so I'm hoping the maintainers of Ubuntu/Fedora/etc have the patches ready for update in the next week or so and this problem will be a thing of the past!

I'm already on vanilla 4.12, no issues so far :)

just had a crash with 4.12 ... nothing in the log after reboot so cannot neither confirm nor deny this was the same crash :(

I'm on 4.10.0-28 right now, and tried almost all kernels downto 4.10.0-19.

Most used case to face this bug is when I'm running VirtualBox and Chrome with lots of opened pages. Few times it happened to me when I open new tab in Chrome. I thought that its all about Chrome and absolutely switched to Firefox. Bug appeared less frequent, but quite stable -- at least twice a day.

Since the bug happens randomly it kills me each time, how can I help you? What kind of information is most helpful to catch the bug?

For me it's always been chrome. After unchecking "use hardware acceleration when available" I've not had it hang again. This is going on 3 weeks now for me. Side effect is that some fancier websites generate some ugly artifacts temporarily at times.

2Matthias As I mentioned, I've tried Firefox too. But got that bug few times.

Agreed. I also saw it with firefox when I tried just swapping out the browser. I'm back to chrome and disabling hardware accelaration has been working for me so far. In the end I'd just really like to see this fixed.

I noticed the HWE kernel rolled from 4.8 to 4.10.0-27-generic, and I wondered if someone knows whether this bug was addressed in that?

There are two patches to address the issue, one for v4.11[1] which can be backported for 4.10 for zesty and current 4.11/master-next branch for artful. The other one has been landed in v4.12[2].

I assume the first patch[1] should be landed for zesty. I can not reproduce the issue on Lenovo Thinkpad X260 with the fix, anyone has the issue can download the prebuilt deb[3] for a test.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=92220696d5d07525443d9280c08c498e77d0386c
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=dd19674bacba227ae5d3ce680cbc5668198894dc
[3] http://people.canonical.com/~chihchun/lp1680904/

I was not expecting the 4.10 kernel to land in the HWE stack for LTS without seeing a fix here, so I am genuinely worried about the LTS+HWE stability now.

Can we get confirmation on the state of the HWE 4.10 kernel?

@ Rex Tsai Thanks for prebuilt kernel. I've installed packages you provided via http://people.canonical.com/~chihchun/lp1680904/

Will try to test it for a while and write if I got any news/conclusions.

I'm a user of the linux-image-generic-hwe-16.04 package on Ubuntu 16.04. Until last weekend, I've never had this issue (using kernel 4.8.x) but today on 4.10.0-27-generic this happened twice to me!

If there's a fix for this issue then it should be merged into this release pretty quick...

@mstucki If you have time, please kindly verify the deb[1] solved your issue.

[1] http://people.canonical.com/~chihchun/lp1680904/

@chihchun does your build contain zfs modules?

@chihchun Thanks, but I'd like to build this on my own. Which patches did you add?

@samvde yes, the build include zfs. The deb is built with Ubuntu zesty kernel tree with the cherry-picked patch.

@mstucki you can cherry pick 1933a35[1] or Chris Wilson's patch[2].

[1] https://patchwork.kernel.org/patch/9789601/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=92220696d5d07525443d9280c08c498e77d0386c

Ok, I'll give it a go.

I can now confirm this bug landed on the LTS HWE kernel.

Honestly, I get Ubuntu for free (well I support them but by no means this is comparable to certain other license schemes out there) but I have never been so disappointed. All my systems are now at risk. I don't know who does QA at Canonical but this really, really sucks.

Downloading debs above for the manual route and crossing my fingers.

I can also confirm this bug with Ubuntu 16.04 and kernel 4.10.0-27-generic on a Dell XPS 13 from 2015.

I had a system freeze yesterday and today. In the months before I never experienced any problems despite heavy swapping.

I can consistently reproduce this issue doing a heavy mail export job in a VirtualBox guest I use for work.

Just having done first run after applying the deb files provided per comment 52, I was not able to reproduce the issue. Thank you @chihchun !

Canonical needs to apply these asap if they want to avoid a catastrophe among their LTS users.

this is ridicules, this bug was reported long time ago (2017-04-07), the patch was created long time ago and here we go.

I might need to abandon the Ubuntu ship and install openSuse or something else where bugs get fixed.

I'm using debs from http://people.canonical.com/~chihchun/lp1680904/ since 2017-07-23 -- lots of heavy work, with VM running almost all time. No crashes happened yet.

I understand that people are *** off by this bug, but keep in mind this bug is not the fault of Canonical or any of the ubuntu developers, this bug actually is the result of the developers at freedesktop/intel pushing their broken code into the mainline kernel release and only (partially) fixing it for the latest (4.12) release (see: https://bugs.freedesktop.org/show_bug.cgi?id=99295).

I found that even with the patch(es) mentioned in the bugreport here and at freedesktop there are still freezes (though less often) (and even on 4.12 (ubuntu mainline) I still have freezes relating to the i915 kernel module) and they probably will also still occur when using CentOS, OpenSuse or any other Linux based distro with kernel 4.10+.

Instead of (non constructive and negatively voiced) reports here I suggest going to the source of the problem and complain there that it is unacceptable that such a major issue has not (yet) resulted in a full revert of the changes that caused it (or a proper fix for all affected kernel versions).

Believe me I already complied there, but nothing happened.

Just had this crash again ( after installing https://wiki.ubuntu.com/Kernel/CrashdumpRecipe )

[19537.273820] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
[19537.273892] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
...
[19537.274570] CPU: 1 PID: 8023 Comm: chrome Not tainted 4.10.0-28-generic #32-Ubuntu

chrome again :(

@flipvb

The main issue is not that this bug exists and that it is not the fault of Canonical. The issue is that the 16.04 stable HWE LTS stack rolled to 4.10 despite this bug being known and being critical, with 16.04.3 not even released yet.

2 Rex Tsai (chihchun)

I've been using your patched kernel since 2017-07-23, but today I've got crash, and it seems quite similar (see attachment).

@Nazar Gerasymchuk (troyan3)
Could you provide the output of "uname -a" on your testing kernel? you might have installed the version from Ubuntu archive without the fix, but not the deb version I built.

@Rex Tsai (chihchun)

It will be ridiculous...

$ uname -a
Linux tro-T460p 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

@Nazar Gerasymchuk (troyan3)
No, you are not using my version. mime is built at Sat Jul 22 12:39:20 UTC 2017.

I've been experimenting with 4.12.3-041203-generic, not crashes but sometimes the screen goes blank for 3 seconds, from syslog

Jul 27 14:50:45 XPS13 org.gnome.Shell.desktop[1986]: intel_do_flush_locked failed: Cannot allocate memory

it recovers nicely, no apps gets killed and nothing gets restarted ( other than gnome desktop ??? )

@chihchun

Out of interest: could you give the procedure how you build this (I've seen various recipes online)?

On my system, your debs are considered a lower version to the repositories that have 4.10.0-28 as well and will offer to "upgrade" it to the official ones every apt upgrade cycle.

So I guess a version bump would be the easiest way to fix this.

Status changed to 'Confirmed' because the bug affects multiple users.

@chichun I've tried installing you debs, but my uname keeps reflecting the Jun 30 date. I pull all the debs and install them with `sudo dpkg -i --force-overwrite *.deb`.

Is there some other magik incantation to force this?

@chihchun Actually I could not install your kernel on 16.04 without breaking dependencies. It requires binutils >= 2.29 (or 2.28, not sure if I remember correctly) but Ubuntu 16.04 only includes version 2.26. So I manually edited the config file in your archive to remove that restriction. I guess other users will be affected by this, too...

Nevertheless, your kernel (4.10.0-28-generic #32 SMP Sat Jul 22 12:39:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux) seems to fix the problem. At least I never had any additional crashes since then...

@matthias-opennomad

I use sudo apt install /directory-with-the-debs/*.deb. Use absolute paths for this.

It warns about downgrading, after which the install runs fine.

@mstucki

Are you running on HWE ?

@s-illes79-gmail New kernel may introduce regression or new issue, I don't think testing 4.12 is in the scope of this bug.
@mstucki You don't need linx*tools* packages.
@samvde Please follow the instruction on wiki[1]. You may have other ppa, apt-cache policy linux-image-4.10.0-28-generic can tell which one is newer than the testing deb.

The prebuilt deb is for testing only, I have proposed the SRU patch[2]

[1] https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
[2] https://lists.ubuntu.com/archives/kernel-team/2017-July/085965.html

@Rex Normally we are asked to test the upstream kernel and I also gave up on ubuntu to fix 4.10.

Right now testing 4.11.12-041112-generic so far this seems to be ok

@s-illes79-gmail developers asked the end user to verify the upstream kernel, it's to identify if it's a regression or fixes have been landed. It helps when we don't know the patch or the root cause of the issue at the early stage.

We know the root cause and patch of this issue, and we also know the patch has been landed after 4.11.6.

4.10 for Ubuntu zesty and HWE kernel should be fixed in next cycle, once the Ubuntu kernel team accept the SRU patch.

Thanks for your feedback and contribution.

@chihchun Many thanks for your work on this issue!

If anyone else is having the issue with running @chichun's kernels, it could be due to the efi.signed image taking precedence. On my Dell XPS 13 the default kernel that boots was `vmlinuz-4.10.0-28-generic.efi.signed`. I forced it to use `vmlinuz-4.10.0-28-generic` and am now running the patched kernel.

The fix for this issue will get committed to the appropriate Ubuntu kernel repositories this week and will be included in the next kernel SRU cycle. Kernels with this fix should be landing in -proposed next week.

@brad-figg Thanks, that's good to hear!

After enabling proposed updates, I see 4.10.0-30-generic is available. Does it already contain the fix?

@philipp-classen

4.10.0-30.34~16.04.1 is a release for CVE-2017-7533 only, it does not contain the patch.
The patch is not been applied in master-next of ubuntu-zesty kernel tree.

Can someone comment here once a fix for the HWE kernel in Ubuntu 16.04 is available? I'm currently using one of the custom builds from earlier in this thread but I haven't yet been able to confirm whether it fixes the issue or not.

@negge The fix for Ubuntu 16.04 (linux-generic-hwe-16.04) has been merged and will be part of the next update (4.10.0-33.37).

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

Just installed the kernel from proposed, if I don't report back that means it works fine.

@kleber-souza It seems like the issue affects both Zesty and Xenial (when using the HWE stack). Does that mean that we need an additional tag "verification-done-xenial" or is it sufficient the way you write it above? Thanks for clarifying!

Can't reproduce the crash as described before (consistently failed on a heavy export job in virtualbox W10 guest).

FWIW the Xenial kernel from -proposed seems to work just fine too.

This bug affects me too.

@Sam Stenvall: How can I install the Xenial kernel from -proposed?

Aug 23 12:31:46 U571T kernel: [40284.307406] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
Aug 23 12:31:46 U571T kernel: [40284.307480] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x124/0x270 [i915]
Aug 23 12:31:46 U571T kernel: [40284.307518] PGD 0
Aug 23 12:31:46 U571T kernel: [40284.307518]
Aug 23 12:31:46 U571T kernel: [40284.307542] Oops: 0002 [#1] SMP
Aug 23 12:31:46 U571T kernel: [40284.307558] Modules linked in: uas usb_storage snd_usb_audio snd_usbmidi_lib cdc_ether usbnet r8152 mii hid_generic ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc aufs rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep binfmt_misc arc4 iwlmvm snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic mac80211 intel_rapl x86_pkg_temp_thermal snd_hda_intel intel_powerclamp snd_hda_codec coretemp kvm_intel snd_hda_core snd_hwdep kvm iwlwifi snd_pcm irqbypass intel_cstate intel_rapl_perf snd_seq_midi snd_seq_midi_event btusb cfg80211 btrtl btbcm btintel bluetooth thinkpad_acpi snd_rawmidi input_leds joydev serio_raw nvram intel_pch_thermal lpc_ich snd_seq snd_seq_device snd_timer
Aug 23 12:31:46 U571T kernel: [40284.307755] snd mei_me mac_hid mei shpchp soundcore ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat libcrc32c nf_conntrack_ftp nf_conntrack iptable_filter ip_tables parport_pc x_tables ppdev lp parport autofs4 algif_skcipher af_alg dm_crypt hid_logitech_hidpp hid_logitech_dj usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect e1000e sysimgblt ahci fb_sys_fops libahci drm ptp pps_core wmi fjes
Aug 23 12:31:46 U571T kernel: [40284.307948] video
Aug 23 12:31:46 U571T kernel: [40284.307957] CPU: 1 PID: 19032 Comm: chrome Tainted: G OE 4.10.0-32-generic #36~16.04.1-Ubuntu
Aug 23 12:31:46 U571T kernel: [40284.307981] Hardware name: LENOVO 20BS0052AD/20BS0052AD, BIOS N14ET24W (1.02 ) 10/27/2014
Aug 23 12:31:46 U571T kernel: [40284.308003] task: ffff9868ed62ad00 task.stack: ffffb32449664000
Aug 23 12:31:46 U571T kernel: [40284.308037] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x124/0x270 [i915]
Aug 23 12:31:46 U571T kernel: [40284.308058] RSP: 0018:ffffb32449667878 EFLAGS: 00010246
Aug 23 12:31:46 U571T kernel: [40284.308073] RAX: ffff98679cbd4a40 RBX: 0000000000000003 RCX: 0000000000000003
Aug 23 12:31:46 U571T kernel: [40284.308092] RDX: 0000000000000000 RSI: ffff9868899c1000 RDI: ffff98691b7d0000
Aug 23 12:31:46 U571T kernel: [40284.308111] RBP: ffffb324496678d8 R08: 0000000000000018 R09: 0000000000000000
Aug 23 12:31:46 U571T kernel: [40284.308130] R10: 0000000000000000 R11: ffffd35...

Enable proposed updates from the "Software updater" application, install whatever updates you get, then disable proposed updates again.

This bug was fixed in the package linux - 4.10.0-33.37

---------------
linux (4.10.0-33.37) zesty; urgency=low

  * linux: 4.10.0-33.37 -proposed tracker (LP: #1709303)

  * CVE-2017-1000112
    - Revert "udp: consistently apply ufo or fragmentation"
    - udp: consistently apply ufo or fragmentation

  * CVE-2017-1000111
    - Revert "net-packet: fix race in packet_set_ring on PACKET_RESERVE"
    - packet: fix tp_reserve race in packet_set_ring

  * ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on
    (LP: #1673564)
    - irqchip/gic-v3: Add missing system register definitions
    - arm64: KVM: Do not use stack-protector to compile EL2 code
    - KVM: arm/arm64: vgic-v3: Use PREbits to infer the number of ICH_APxRn_EL2
      registers
    - KVM: arm/arm64: vgic-v3: Fix nr_pre_bits bitfield extraction
    - arm64: Add a facility to turn an ESR syndrome into a sysreg encoding
    - KVM: arm/arm64: vgic-v3: Add accessors for the ICH_APxRn_EL2 registers
    - KVM: arm64: Make kvm_condition_valid32() accessible from EL2
    - KVM: arm64: vgic-v3: Add hook to handle guest GICv3 sysreg accesses at EL2
    - KVM: arm64: vgic-v3: Add ICV_BPR1_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_IGRPEN1_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_IAR1_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_EOIR1_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_AP1Rn_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_HPPIR1_EL1 handler
    - KVM: arm64: vgic-v3: Enable trapping of Group-1 system registers
    - KVM: arm64: Enable GICv3 Group-1 sysreg trapping via command-line
    - KVM: arm64: vgic-v3: Add ICV_BPR0_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_IGNREN0_EL1 handler
    - KVM: arm64: vgic-v3: Add misc Group-0 handlers
    - KVM: arm64: vgic-v3: Enable trapping of Group-0 system registers
    - KVM: arm64: Enable GICv3 Group-0 sysreg trapping via command-line
    - arm64: Add MIDR values for Cavium cn83XX SoCs
    - [Config] CONFIG_CAVIUM_ERRATUM_30115=y
    - arm64: Add workaround for Cavium Thunder erratum 30115
    - KVM: arm64: vgic-v3: Add ICV_DIR_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_RPR_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_CTLR_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_PMR_EL1 handler
    - KVM: arm64: Enable GICv3 common sysreg trapping via command-line
    - KVM: arm64: vgic-v3: Log which GICv3 system registers are trapped
    - arm64: KVM: Make unexpected reads from WO registers inject an undef
    - KVM: arm64: Log an error if trapping a read-from-write-only GICv3 access
    - KVM: arm64: Log an error if trapping a write-to-read-only GICv3 access

  * ibmvscsis: Do not send aborted task response (LP: #1689365)
    - target: Fix unknown fabric callback queue-full errors
    - ibmvscsis: Do not send aborted task response
    - ibmvscsis: Clear left-over abort_cmd pointers
    - ibmvscsis: Fix the incorrect req_lim_delta

  * hisi_sas performance improvements (LP: #1708734)
    - scsi: hisi_sas: define hisi_sas_device.device_id as int
    - scsi: hisi_sas: optimise the usage of hisi_hba.lock
    - scsi: hisi_sas: relocate sata_done_v2_hw()
    - scsi: hisi_sas: optimise DMA slot memory

  * hisi_sas...

This bug was fixed in the package linux-hwe - 4.10.0-33.37~16.04.1

---------------
linux-hwe (4.10.0-33.37~16.04.1) xenial; urgency=low

  * linux-hwe: 4.10.0-33.37~16.04.1 -proposed tracker (LP: #1709304)

  * linux: 4.10.0-33.37 -proposed tracker (LP: #1709303)

  * CVE-2017-1000112
    - Revert "udp: consistently apply ufo or fragmentation"
    - udp: consistently apply ufo or fragmentation

  * CVE-2017-1000111
    - Revert "net-packet: fix race in packet_set_ring on PACKET_RESERVE"
    - packet: fix tp_reserve race in packet_set_ring

  * ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on
    (LP: #1673564)
    - irqchip/gic-v3: Add missing system register definitions
    - arm64: KVM: Do not use stack-protector to compile EL2 code
    - KVM: arm/arm64: vgic-v3: Use PREbits to infer the number of ICH_APxRn_EL2
      registers
    - KVM: arm/arm64: vgic-v3: Fix nr_pre_bits bitfield extraction
    - arm64: Add a facility to turn an ESR syndrome into a sysreg encoding
    - KVM: arm/arm64: vgic-v3: Add accessors for the ICH_APxRn_EL2 registers
    - KVM: arm64: Make kvm_condition_valid32() accessible from EL2
    - KVM: arm64: vgic-v3: Add hook to handle guest GICv3 sysreg accesses at EL2
    - KVM: arm64: vgic-v3: Add ICV_BPR1_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_IGRPEN1_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_IAR1_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_EOIR1_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_AP1Rn_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_HPPIR1_EL1 handler
    - KVM: arm64: vgic-v3: Enable trapping of Group-1 system registers
    - KVM: arm64: Enable GICv3 Group-1 sysreg trapping via command-line
    - KVM: arm64: vgic-v3: Add ICV_BPR0_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_IGNREN0_EL1 handler
    - KVM: arm64: vgic-v3: Add misc Group-0 handlers
    - KVM: arm64: vgic-v3: Enable trapping of Group-0 system registers
    - KVM: arm64: Enable GICv3 Group-0 sysreg trapping via command-line
    - arm64: Add MIDR values for Cavium cn83XX SoCs
    - [Config] CONFIG_CAVIUM_ERRATUM_30115=y
    - arm64: Add workaround for Cavium Thunder erratum 30115
    - KVM: arm64: vgic-v3: Add ICV_DIR_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_RPR_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_CTLR_EL1 handler
    - KVM: arm64: vgic-v3: Add ICV_PMR_EL1 handler
    - KVM: arm64: Enable GICv3 common sysreg trapping via command-line
    - KVM: arm64: vgic-v3: Log which GICv3 system registers are trapped
    - arm64: KVM: Make unexpected reads from WO registers inject an undef
    - KVM: arm64: Log an error if trapping a read-from-write-only GICv3 access
    - KVM: arm64: Log an error if trapping a write-to-read-only GICv3 access

  * ibmvscsis: Do not send aborted task response (LP: #1689365)
    - target: Fix unknown fabric callback queue-full errors
    - ibmvscsis: Do not send aborted task response
    - ibmvscsis: Clear left-over abort_cmd pointers
    - ibmvscsis: Fix the incorrect req_lim_delta

  * hisi_sas performance improvements (LP: #1708734)
    - scsi: hisi_sas: define hisi_sas_device.device_id as int
    - scsi: hisi_sas: optimise the usage of hisi_hba.lock
    - scsi: hi...

just happened for me running 4.10.10-041010-generic running google-chrome-beta, went to this page : http://www.abc.net.au/news/2017-10-16/north-korea-missile-range-map/8880894 . If you're running vanilla kernels you need 4.11.6 I think? https://bugs.freedesktop.org/show_bug.cgi?id=99295