Freeze

Bug #1699902 reported by Roman Odaisky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Out of nowhere, my OS froze, failing to respond to anything but the SysRq reboot.

The following was logged:

Jun 22 18:06:43 zen kernel: [64494.503613] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
Jun 22 18:06:43 zen kernel: [64494.503675] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
Jun 22 18:06:43 zen kernel: [64494.503695] PGD 0
Jun 22 18:06:43 zen kernel: [64494.503695]
Jun 22 18:06:43 zen kernel: [64494.503708] Oops: 0002 [#1] SMP
Jun 22 18:06:43 zen kernel: [64494.503719] Modules linked in: ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc nls_iso8859_1 asus_nb_wmi asus_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_conexant snd_hda_codec_hdmi snd_hda_codec_generic kvm snd_hda_intel snd_hda_codec irqbypass snd_hda_core crct10dif_pclmul arc4 crc32_pclmul snd_hwdep ghash_clmulni_intel snd_pcm uvcvideo pcbc videobuf2_vmalloc snd_seq_midi videobuf2_memops aesni_intel snd_seq_midi_event btusb videobuf2_v4l2 aes_x86_64 videobuf2_core btrtl crypto_simd btbcm videodev glue_helper media cryptd btintel iwlmvm bluetooth snd_rawmidi intel_cstate
Jun 22 18:06:43 zen kernel: [64494.503916] mac80211 intel_rapl_perf snd_seq joydev input_leds iwlwifi snd_seq_device serio_raw snd_timer intel_pch_thermal cfg80211 snd mei_me processor_thermal_device mei lpc_ich soundcore intel_soc_dts_iosf shpchp dw_dmac dw_dmac_core snd_soc_sst_acpi snd_soc_sst_match i2c_designware_platform 8250_dw int3400_thermal i2c_designware_core acpi_als kfifo_buf acpi_thermal_rel industrialio mac_hid acpi_pad int3402_thermal int3406_thermal int340x_thermal_zone spi_pxa2xx_platform asus_wireless parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq hid_generic usbhid hid i915 i2c_algo_bit psmouse drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ahci libahci wmi sdhci_acpi sdhci video fjes
Jun 22 18:06:43 zen kernel: [64494.504109] CPU: 2 PID: 3624 Comm: chromium-browse Tainted: G OE 4.10.0-22-generic #24-Ubuntu
Jun 22 18:06:43 zen kernel: [64494.504133] Hardware name: ASUSTeK COMPUTER INC. UX305LA/UX305LA, BIOS UX305LA.206 08/03/2015
Jun 22 18:06:43 zen kernel: [64494.504156] task: ffff9f53361a9680 task.stack: ffffac77c8738000
Jun 22 18:06:43 zen kernel: [64494.504194] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
Jun 22 18:06:43 zen kernel: [64494.504225] RSP: 0018:ffffac77c873b880 EFLAGS: 00010246
Jun 22 18:06:43 zen kernel: [64494.504240] RAX: ffff9f538d911e40 RBX: 0000000000000003 RCX: 0000000000000003
Jun 22 18:06:43 zen kernel: [64494.504258] RDX: 0000000000000000 RSI: ffff9f52ca31b000 RDI: ffff9f53fb860000
Jun 22 18:06:43 zen kernel: [64494.504277] RBP: ffffac77c873b8d8 R08: 0000000000000000 R09: 0000000000000000
Jun 22 18:06:43 zen kernel: [64494.504296] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9f53f75a0000
Jun 22 18:06:43 zen kernel: [64494.504315] R13: ffff9f54010f6ad0 R14: 00000000fffdf000 R15: 0000000000008000
Jun 22 18:06:43 zen kernel: [64494.504334] FS: 00007fe1c6381180(0000) GS:ffff9f540ed00000(0000) knlGS:0000000000000000
Jun 22 18:06:43 zen kernel: [64494.504355] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 22 18:06:43 zen kernel: [64494.504375] CR2: 0000000000000018 CR3: 000000018803e000 CR4: 00000000003406e0
Jun 22 18:06:43 zen kernel: [64494.504408] Call Trace:
Jun 22 18:06:43 zen kernel: [64494.504429] gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
Jun 22 18:06:43 zen kernel: [64494.504445] ? __switch_to+0x23c/0x520
Jun 22 18:06:43 zen kernel: [64494.504468] gen8_alloc_va_range+0x23d/0x470 [i915]
Jun 22 18:06:43 zen kernel: [64494.504498] i915_vma_bind+0x7e/0x170 [i915]
Jun 22 18:06:43 zen kernel: [64494.504527] __i915_vma_do_pin+0x2a5/0x450 [i915]
Jun 22 18:06:43 zen kernel: [64494.504559] i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
Jun 22 18:06:43 zen kernel: [64494.504601] i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
Jun 22 18:06:43 zen kernel: [64494.504650] i915_gem_do_execbuffer.isra.38+0x4ca/0x15c0 [i915]
Jun 22 18:06:43 zen kernel: [64494.504681] ? find_get_entry+0x20/0x100
Jun 22 18:06:43 zen kernel: [64494.504704] ? shmem_getpage_gfp+0xf9/0xc10
Jun 22 18:06:43 zen kernel: [64494.504733] i915_gem_execbuffer2+0xa1/0x1e0 [i915]
Jun 22 18:06:43 zen kernel: [64494.504758] drm_ioctl+0x21b/0x4c0 [drm]
Jun 22 18:06:43 zen kernel: [64494.504784] ? i915_gem_execbuffer+0x310/0x310 [i915]
Jun 22 18:06:43 zen kernel: [64494.504802] ? __seccomp_filter+0x67/0x250
Jun 22 18:06:43 zen kernel: [64494.504817] do_vfs_ioctl+0xa3/0x610
Jun 22 18:06:43 zen kernel: [64494.504832] ? __secure_computing+0x3f/0xd0
Jun 22 18:06:43 zen kernel: [64494.504848] ? syscall_trace_enter+0xcd/0x2e0
Jun 22 18:06:43 zen kernel: [64494.504864] SyS_ioctl+0x79/0x90
Jun 22 18:06:43 zen kernel: [64494.504880] do_syscall_64+0x5b/0xc0
Jun 22 18:06:43 zen kernel: [64494.504893] entry_SYSCALL64_slow_path+0x25/0x25
Jun 22 18:06:43 zen kernel: [64494.504912] RIP: 0033:0x7fe1b0e91987
Jun 22 18:06:43 zen kernel: [64494.504931] RSP: 002b:00007ffe79637568 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jun 22 18:06:43 zen kernel: [64494.504966] RAX: ffffffffffffffda RBX: 00005614a5d83cc0 RCX: 00007fe1b0e91987
Jun 22 18:06:43 zen kernel: [64494.504985] RDX: 00007ffe796375b0 RSI: 00000000c0406469 RDI: 00000000000000f1
Jun 22 18:06:43 zen kernel: [64494.505003] RBP: 00007ffe796375b0 R08: 0000000000000000 R09: 0000000000000000
Jun 22 18:06:43 zen kernel: [64494.505022] R10: 0000000000000038 R11: 0000000000000246 R12: 00000000c0406469
Jun 22 18:06:43 zen kernel: [64494.505040] R13: 00000000000000f1 R14: 0000000000000000 R15: 0000000000000000
Jun 22 18:06:43 zen kernel: [64494.505058] Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 aa cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 08 0f 1f 44 00 00 e9 53 ff ff ff 65 8b 05
Jun 22 18:06:43 zen kernel: [64494.505133] RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: ffffac77c873b880
Jun 22 18:06:43 zen kernel: [64494.505155] CR2: 0000000000000018
Jun 22 18:06:43 zen kernel: [64494.535476] ---[ end trace e58506fac3127636 ]---

The log went on to record the fact that I unplugged my mouse and plugged it back (I first thought that was the problem), so the system wasn’t completely frozen, only the screen was (and Ctrl+Alt+F1 did nothing). I missed the chance to attempt an SSH connection, should I try that and do anything in particular in case the problem reappears?

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-generic 4.10.0.22.24
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Jun 23 01:04:00 2017
HibernationDevice: RESUME=UUID=d6fabf37-7e01-4470-bae0-3ebc4313d707
InstallationDate: Installed on 2015-12-17 (553 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
 Bus 001 Device 003: ID 8087:0a2a Intel Corp.
 Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX305LA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-22-generic.efi.signed root=/dev/mapper/vgzen-root ro rootflags=subvol=@ quiet splash crashkernel=384M-:128M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-22-generic N/A
 linux-backports-modules-4.10.0-22-generic N/A
 linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-06-16 (6 days ago)
dmi.bios.date: 08/03/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305LA.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305LA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305LA.206:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnUX305LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX305LA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Roman Odaisky (to-roma-from-lp) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) 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.12 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.12

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.