GPU crash on NUC with i915

Bug #1488758 reported by Alexander List on 2015-08-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned

Bug Description

Setup:

Intel NUC, i915 graphics, two monitors, one connected with miniHDMI->HDMI cable, second with miniDP->HDMI cable.

Screen goes black, flickers back on, goes black again. Only resolution is to ssh into the machine and reboot.

Before rebooting, I got lots of these (about 106k lines) in syslog:

kernel: [404964.521324] [drm:hsw_unclaimed_reg_detect.isra.12 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.[drm:hsw_unclaimed_reg_detect.isra.12 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.

...then,

kernel: [406333.381029] [drm] stuck on render ring
kernel: [406333.381945] [drm] GPU HANG: ecode 8:0:0xf5dffffe, in Xorg [918], reason: Ring hung, action: reset
kernel: [406333.381947] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
kernel: [406333.381947] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
kernel: [406333.381948] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
kernel: [406333.381949] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
kernel: [406333.381951] [drm] GPU crash dump saved to /sys/class/drm/card0/error
kernel: [406333.389006] drm/i915: Resetting chip after gpu hang
kernel: [406339.379515] [drm] stuck on render ring
kernel: [406339.380430] [drm] GPU HANG: ecode 8:0:0x85dffffb, in webapp-containe [14994], reason: Ring hung, action: reset
kernel: [406339.380583] drm/i915: Resetting chip after gpu hang
kernel: [406417.336790] [drm] GPU HANG: ecode 8:0:0xf5dffffe, in Xorg [918], reason: Ring hung, action: reset
kernel: [406417.343850] drm/i915: Resetting chip after gpu hang
kernel: [407944.976072] [drm] GPU HANG: ecode 8:0:0xf5dffffe, in Xorg [918], reason: Ring hung, action: reset
kernel: [407944.983106] drm/i915: Resetting chip after gpu hang
kernel: [409258.618636] [drm] GPU HANG: ecode 8:0:0xf5dffffe, in Xorg [918], reason: Ring hung, action: reset
kernel: [409258.625733] drm/i915: Resetting chip after gpu hang
kernel: [409264.604180] [drm] stuck on render ring
kernel: [409264.605059] [drm] GPU HANG: ecode 8:0:0xf5dffffe, in Xorg [918], reason: Ring hung, action: reset
kernel: [409264.605153] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning!
kernel: [409264.612163] drm/i915: Resetting chip after gpu hang

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-26-generic 3.19.0-26.28
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
Date: Wed Aug 26 12:31:15 2015
InstallationDate: Installed on 2015-08-01 (24 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)

Alexander List (alexlist) wrote :
Alexander List (alexlist) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Critical

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.19.0-15.15
Alexander List (alexlist) wrote :

This problem occured once in two months, and we are not aware of a way to trigger it. However, there is a clear indication that the bug is well known upstream, so it should be followed up with in Ubuntu as well.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: bot-stop-nagging
Changed in linux (Ubuntu):
importance: Critical → High
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.