[Bug 93510] drm/i915: Resetting chip after gpu hang

[bugzilla-daemon at freedesktop.org]

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

--- Comment #3 from Luís Silva <luisbite+freedesktop at gmail.com> ---
It happened again to me. Same thing (drm/i915: Resetting chip after gpu hang).
This time I was using GIMP.

$ dmesg
(...)
[34084.816870] [drm] GPU HANG: ecode 3:0:0x757fffc1, in Xorg [828], reason:
Ring hung, action: reset
[34084.816874] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[34084.816877] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[34084.816880] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[34084.816883] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[34084.816886] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[34084.816974] ------------[ cut here ]------------
[34084.817045] WARNING: CPU: 0 PID: 5845 at
/build/linux-cRemOf/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:3296
intel_crtc_wait_for_pending_flips+0x192/0x230 [i915]()
[34084.817049] WARN_ON(ret)
[34084.817052] Modules linked in:
[34084.817056]  drbg ansi_cprng xts gf128mul dm_crypt snd_hda_codec_realtek
snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core input_leds
joydev snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq
snd_seq_device snd_timer gpio_ich snd soundcore coretemp lpc_ich shpchp pcspkr
8250_fintek serio_raw asus_atk0110 mac_hid parport_pc ppdev lp parport autofs4
hid_generic usbhid pata_acpi i915 hid video i2c_algo_bit drm_kms_helper atl2
drm
[34084.817122] CPU: 0 PID: 5845 Comm: kworker/u8:0 Not tainted 4.2.0-22-generic
#27-Ubuntu
[34084.817126] Hardware name: System manufacturer System Product
Name/P5GC-MX/1333, BIOS 0413    03/13/2009
[34084.817163] Workqueue: i915-hangcheck i915_hangcheck_elapsed [i915]
[34084.817168]  0000000000000000 00000000ad528bbb ffff88005cc03a78
ffffffff817e94c9
[34084.817174]  0000000000000000 ffff88005cc03ad0 ffff88005cc03ab8
ffffffff8107b3d6
[34084.817180]  ffff88005cc03ab8 ffff880035410000 0000000000000001
ffff8800763ed000
[34084.817186] Call Trace:
[34084.817196]  [<ffffffff817e94c9>] dump_stack+0x45/0x57
[34084.817204]  [<ffffffff8107b3d6>] warn_slowpath_common+0x86/0xc0
[34084.817209]  [<ffffffff8107b465>] warn_slowpath_fmt+0x55/0x70
[34084.817242]  [<ffffffffc01366fd>] ? i915_gem_object_wait_rendering+0x6d/0xc0
[i915]
[34084.817281]  [<ffffffffc0178942>]
intel_crtc_wait_for_pending_flips+0x192/0x230 [i915]
[34084.817320]  [<ffffffffc0039bf0>] ? drm_modeset_lock_all_crtcs+0x90/0xa0
[drm]
[34084.817359]  [<ffffffffc0179d42>] intel_crtc_disable_planes+0x32/0x100
[i915]
[34084.817397]  [<ffffffffc0179ed5>] intel_prepare_reset+0x75/0x90 [i915]
[34084.817431]  [<ffffffffc01463b2>] i915_reset_and_wakeup+0xe2/0x170 [i915]
[34084.817467]  [<ffffffffc014af3a>] i915_handle_error+0xca/0x660 [i915]
[34084.817473]  [<ffffffff810d200e>] ? vprintk_emit+0x2de/0x530
[34084.817479]  [<ffffffff817e6b76>] ? printk+0x55/0x6b
[34084.817513]  [<ffffffffc014b795>] i915_hangcheck_elapsed+0x275/0x470 [i915]
[34084.817521]  [<ffffffff810941ca>] process_one_work+0x1aa/0x440
[34084.817526]  [<ffffffff810944ab>] worker_thread+0x4b/0x4c0
[34084.817531]  [<ffffffff81094460>] ? process_one_work+0x440/0x440
[34084.817537]  [<ffffffff8109a868>] kthread+0xd8/0xf0
[34084.817543]  [<ffffffff8109a790>] ? kthread_create_on_node+0x1f0/0x1f0
[34084.817548]  [<ffffffff817f06df>] ret_from_fork+0x3f/0x70
[34084.817552]  [<ffffffff8109a790>] ? kthread_create_on_node+0x1f0/0x1f0
[34084.817556] ---[ end trace b494de9c54078aea ]---
[34084.843918] drm/i915: Resetting chip after gpu hang.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20151229/f62fc9b1/attachment.html>