Bug 79505 - [gen3] Display A: Invalid tiling
Summary: [gen3] Display A: Invalid tiling
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
: 79859 79876 80377 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-06-01 14:22 UTC by Francesco Turco
Modified: 2017-07-24 22:54 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:

Attachments
/sys/class/drm/card0/error (674.96 KB, text/plain)
2014-06-01 14:22 UTC, Francesco Turco 		no flags Details
/sys/class/drm/card0/error with kernel 3.12.20 (701.26 KB, text/plain)
2014-06-02 18:31 UTC, Francesco Turco 		no flags Details
/sys/class/drm/card0/error with kernel 3.15.0 (703.94 KB, text/plain)
2014-06-14 17:38 UTC, Francesco Turco 		no flags Details
fix error dump (1.97 KB, patch)
2014-06-14 18:02 UTC, Imre Deak 		no flags Details | Splinter Review
/sys/class/drm/card0/error with kernel from git (702.10 KB, text/plain)
2014-06-14 20:17 UTC, Francesco Turco 		no flags Details
/sys/class/drm/card0/error-3.17.0-rc2+ (675.54 KB, text/plain)
2014-09-02 03:52 UTC, Priit Laes (irc: plaes) 		no flags Details
View All

Description Francesco Turco 2014-06-01 14:22:16 UTC 
Created attachment 100236 [details]
/sys/class/drm/card0/error

I have a Gentoo Linux system and a Intel DQ35JO motherboard with and integrated video chipset. I was using GNOME 3.12 when the screen suddently froze, except for the mouse pointer.

These are the relevant entries from the journalctl log:

Jun 01 15:57:15 desktop kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jun 01 15:57:15 desktop kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jun 01 15:57:15 desktop kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jun 01 15:57:15 desktop kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jun 01 15:57:15 desktop kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jun 01 15:57:15 desktop kernel: i915: render error detected, EIR: 0x00000010
Jun 01 15:57:15 desktop kernel: i915: page table error
Jun 01 15:57:15 desktop kernel: i915:   PGTBL_ER: 0x00000040
Jun 01 15:57:15 desktop kernel: [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
Jun 01 15:57:15 desktop kernel: i915: render error detected, EIR: 0x00000010
Jun 01 15:57:15 desktop kernel: i915: page table error
Jun 01 15:57:15 desktop kernel: i915:   PGTBL_ER: 0x00000040
[...]
Jun 01 15:57:40 desktop kernel: [drm] stuck on render ring
Jun 01 15:57:40 desktop kernel: [drm:i915_reset] *ERROR* Failed to reset chip: -19

I attached the content of the file /sys/class/drm/card0/error.

I'm using the following packages:
- media-libs/mesa-10.1.4:0
- x11-base/xorg-server-1.15.1
- x11-drivers/xf86-video-intel-2.99.911-r1
- sys-kernel/gentoo-sources-3.14.4

Please tell me if you need other informations.
Comment 1 Chris Wilson 2014-06-01 15:32:04 UTC 
Great, the error capture is bust:

Num Pipes: 2
Pipe [0]:
  Power: off
  SRC: 00000000
Plane [0]:
  CNTR: 00000000
  STRIDE: 00000000
  SIZE: 00000000
  POS: 00000000
  ADDR: 00000000
Cursor [0]:
  CNTR: 00000000
  POS: 00000000
  BASE: 00000000
Pipe [1]:
  Power: off
  SRC: 00000000
Plane [1]:
  CNTR: 00000000
  STRIDE: 00000000
  SIZE: 00000000
  POS: 00000000
  ADDR: 00000000
Cursor [1]:
  CNTR: 00000000
  POS: 00000000
  BASE: 00000000
CPU transcoder: A
  Power: off
  CONF: 00000000
  HTOTAL: 00000000
  HBLANK: 00000000
  HSYNC: 00000000
  VTOTAL: 00000000
  VBLANK: 00000000
  VSYNC: 00000000
CPU transcoder: A
  Power: off
  CONF: 00000000
  HTOTAL: 00000000
  HBLANK: 00000000
  HSYNC: 00000000
  VTOTAL: 00000000
  VBLANK: 00000000
  VSYNC: 00000000
Comment 2 Chris Wilson 2014-06-02 07:39:34 UTC 
Sadly the information captured here is insufficient to identify the cause. If you can reproduce this with either an older or newer kernel, that may help (if the error state has the right information).
Comment 3 Francesco Turco 2014-06-02 17:31:28 UTC 
I will try with another kernel later. In the meantime it crashed another time, and the error file still shows a bunch of zeroes only. But journalctl also shows the following things from gdm-Xorg (may be helpful):

Jun 02 19:16:12 desktop gdm-Xorg-:0[169]: (EE) [mi] EQ overflowing.  Additional events will be discarded until existing events are processed.
Jun 02 19:16:12 desktop gdm-Xorg-:0[169]: (EE)
Jun 02 19:16:12 desktop gdm-Xorg-:0[169]: (EE) Backtrace:
Jun 02 19:16:12 desktop gdm-Xorg-:0[169]: (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x48) [0x5808b8]
Jun 02 19:16:12 desktop gdm-Xorg-:0[169]: (EE) 1: /usr/bin/Xorg (mieqEnqueue+0x22b) [0x562beb]
Jun 02 19:16:12 desktop gdm-Xorg-:0[169]: (EE) 2: /usr/bin/Xorg (QueuePointerEvents+0x52) [0x44c492]
Jun 02 19:16:12 desktop gdm-Xorg-:0[169]: (EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fee921fe000+0x579d) [0x7fee9220379d]
Jun 02 19:16:12 desktop gdm-Xorg-:0[169]: (EE) 4: /usr/bin/Xorg (0x400000+0x71f78) [0x471f78]
Jun 02 19:16:12 desktop gdm-Xorg-:0[169]: (EE) 5: /usr/bin/Xorg (0x400000+0x9a010) [0x49a010]
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) 6: /lib64/libpthread.so.0 (0x7fee99419000+0x11250) [0x7fee9942a250]
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) 7: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fee953c4000+0xac2f5) [0x7fee954702f5]
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fee953c4000+0x8c964) [0x7fee95450964]
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) 9: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fee953c4000+0x9050b) [0x7fee9545450b]
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) 10: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fee953c4000+0x765ea) [0x7fee9543a5ea]
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) 11: /usr/bin/Xorg (0x400000+0x102f63) [0x502f63]
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) 12: /usr/bin/Xorg (0x400000+0x3584e) [0x43584e]
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) 13: /usr/bin/Xorg (0x400000+0x3965a) [0x43965a]
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) 14: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7fee980a3db5]
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) 15: /usr/bin/Xorg (0x400000+0x24e71) [0x424e71]
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE)
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: (EE) [mi] mieq is *NOT* the cause.  It is a victim.
Jun 02 19:16:13 desktop kernel: [drm] stuck on render ring
Jun 02 19:16:13 desktop kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jun 02 19:16:13 desktop kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jun 02 19:16:13 desktop kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jun 02 19:16:13 desktop kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jun 02 19:16:13 desktop kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jun 02 19:16:13 desktop kernel: [drm:i915_reset] *ERROR* Failed to reset chip: -19
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: [mi] Increasing EQ size to 1024 to prevent dropped events.
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: [mi] EQ processing has resumed after 29 dropped events.
Jun 02 19:16:13 desktop gdm-Xorg-:0[169]: [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
Jun 02 19:16:33 desktop gdm-Xorg-:0[169]: (EE) intel(0): Detected a hung GPU, disabling acceleration.
Jun 02 19:16:33 desktop gdm-Xorg-:0[169]: (EE) intel(0): When reporting this, please include /sys/class/drm/card0/error and the full dmesg.
Jun 02 19:16:33 desktop gdm-Xorg-:0[169]: (II) AIGLX: Suspending AIGLX clients for VT switch
Comment 4 Francesco Turco 2014-06-02 18:30:53 UTC 
I tried kernel 3.12.20 and it crashed again. This time the error log looks good, as there are many non-zero values.

These are the corresponding log messages from journalctl:

Jun 02 20:24:05 desktop kernel: [drm] stuck on render ring
Jun 02 20:24:05 desktop kernel: [drm] capturing error event; look for more information in /sys/class/drm/card0/error
Jun 02 20:24:05 desktop kernel: [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x700000 ctx 0) at 0x700198
Jun 02 20:24:05 desktop kernel: [drm:i915_reset] *ERROR* Failed to reset chip.
Jun 02 20:24:20 desktop gdm-Xorg-:0[156]: (EE) intel(0): Detected a hung GPU, disabling acceleration.
Jun 02 20:24:20 desktop gdm-Xorg-:0[156]: (EE) intel(0): When reporting this, please include /sys/class/drm/card0/error and the full dmesg.
Jun 02 20:24:25 desktop kernel: uhci_hcd 0000:00:1a.2: release dev 2 ep81-INT, period 8, phase 4, 93 us
Jun 02 20:24:25 desktop gdm-Xorg-:0[156]: (II) AIGLX: Suspending AIGLX clients for VT switch
Comment 5 Francesco Turco 2014-06-02 18:31:52 UTC 
Created attachment 100330 [details]
/sys/class/drm/card0/error with kernel 3.12.20
Comment 6 Chris Wilson 2014-06-10 09:09:56 UTC 
*** Bug 79859 has been marked as a duplicate of this bug. ***
Comment 7 Chris Wilson 2014-06-10 11:13:35 UTC 
*** Bug 79876 has been marked as a duplicate of this bug. ***
Comment 8 Chris Wilson 2014-06-10 15:57:57 UTC 
*** Bug 79859 has been marked as a duplicate of this bug. ***
Comment 9 Imre Deak 2014-06-13 12:58:19 UTC 
Francesco, any chance you could try with your kernel

commit b8c000d9bf23e7c1155ef421f595d1cbc25262da
Author: Imre Deak <imre.deak@intel.com>
Date:   Mon Jun 2 14:21:10 2014 +0300

and provide a new error state dump? This commit is in Linus' tree.
Comment 10 Francesco Turco 2014-06-13 18:44:29 UTC 
I'm not an expert with Git commits or kernel development... I tried finding the commit you specified but was not able to find it. What kernel should I try? 3.15.x? 3.14.x? 3.12.x?
Comment 11 Priit Laes (irc: plaes) 2014-06-13 18:54:09 UTC 
(In reply to comment #10)
> I'm not an expert with Git commits or kernel development... I tried finding
> the commit you specified but was not able to find it. What kernel should I
> try? 3.15.x? 3.14.x? 3.12.x?

This is currently in 3.15.0+, which is the new development kernel.

I was one of the people who was bitten this bug and probably the same issue. I'm currently running kernel with this patch enabled, so if you are unable to upgrade meanwhile, don't worry.
Comment 12 Francesco Turco 2014-06-14 17:38:02 UTC 
Created attachment 101058 [details]
/sys/class/drm/card0/error with kernel 3.15.0
Comment 13 Francesco Turco 2014-06-14 17:45:42 UTC 
From journalctl:


Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) [mi] EQ overflowing.  Additional events will be discarded until existing events are processed.
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE)
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) Backtrace:
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x48) [0x5808b8]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 1: /usr/bin/Xorg (mieqEnqueue+0x22b) [0x562beb]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 2: /usr/bin/Xorg (QueuePointerEvents+0x52) [0x44c492]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fd05cd73000+0x579d) [0x7fd05cd7879d]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 4: /usr/bin/Xorg (0x400000+0x71f78) [0x471f78]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 5: /usr/bin/Xorg (0x400000+0x9a010) [0x49a010]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 6: /lib64/libpthread.so.0 (0x7fd064da4000+0x11250) [0x7fd064db5250]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 7: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fd060738000+0xa85a8) [0x7fd0607e05a8]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fd060738000+0x688f6) [0x7fd0607a08f6]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 9: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7fd060738000+0x6d5e1) [0x7fd0607a55e1]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 10: /usr/bin/Xorg (0x400000+0x10c456) [0x50c456]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 11: /usr/bin/Xorg (0x400000+0x1028fe) [0x5028fe]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 12: /usr/bin/Xorg (0x400000+0x3584e) [0x43584e]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 13: /usr/bin/Xorg (0x400000+0x3965a) [0x43965a]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 14: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7fd063a2edb5]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) 15: /usr/bin/Xorg (0x400000+0x24e71) [0x424e71]
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE)
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
Jun 14 19:31:33 desktop gdm-Xorg-:0[165]: (EE) [mi] mieq is *NOT* the cause.  It is a victim.
Jun 14 19:31:36 desktop kernel: [drm] stuck on render ring
Jun 14 19:31:36 desktop gdm-Xorg-:0[165]: [mi] Increasing EQ size to 1024 to prevent dropped events.
Jun 14 19:31:36 desktop kernel: [drm] GPU HANG: ecode 0:0x028df8c7, in gnome-shell [548], reason: Ring hung, action: reset
Jun 14 19:31:36 desktop kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jun 14 19:31:36 desktop kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jun 14 19:31:36 desktop kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jun 14 19:31:36 desktop kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jun 14 19:31:36 desktop kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jun 14 19:31:36 desktop kernel: [drm:i915_reset] *ERROR* Failed to reset chip: -19
Jun 14 19:31:36 desktop gdm-Xorg-:0[165]: [mi] EQ processing has resumed after 28 dropped events.
Jun 14 19:31:36 desktop gdm-Xorg-:0[165]: [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
Jun 14 19:31:36 desktop gdm-Xorg-:0[165]: (EE) intel(0): Detected a hung GPU, disabling acceleration.
Jun 14 19:31:36 desktop gdm-Xorg-:0[165]: (EE) intel(0): When reporting this, please include /sys/class/drm/card0/error and the full dmesg.
Jun 14 19:31:36 desktop kernel: ------------[ cut here ]------------
Jun 14 19:31:36 desktop kernel: WARNING: CPU: 1 PID: 165 at drivers/gpu/drm/drm_irq.c:770 send_vblank_event+0xac/0x100 [drm]()
Jun 14 19:31:36 desktop kernel: Modules linked in: usbhid snd_hda_codec_realtek snd_hda_codec_generic coretemp hwmon kvm_intel kvm microcode pcspkr i2c_i801 uhci_hcd i915 cfbfillrect cfbimgblt snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep i2c_algo_bit snd_pcm cfbcopyarea drm_kms_helper snd_timer drm snd intel_agp intel_gtt ehci_pci ehci_hcd usbcore rtc_cmos agpgart evdev usb_common e1000e soundcore ipv6
Jun 14 19:31:36 desktop kernel: CPU: 1 PID: 165 Comm: Xorg Not tainted 3.15.0-gentoo-r1-first #1
Jun 14 19:31:36 desktop kernel: Hardware name:                  /DQ35JO, BIOS JOQ3510J.86A.1143.2010.1209.0048 12/09/2010
Jun 14 19:31:36 desktop kernel:  0000000000000009 ffff880221877c58 ffffffff8141ce58 0000000000000000
Jun 14 19:31:36 desktop kernel:  ffff880221877c90 ffffffff8103bbc8 ffff8801ec811540 ffff88022199a000
Jun 14 19:31:36 desktop kernel:  ffff880220448780 ffff880221f9e000 ffff88022199a200 ffff880221877ca0
Jun 14 19:31:36 desktop kernel: Call Trace:
Jun 14 19:31:36 desktop kernel:  [<ffffffff8141ce58>] dump_stack+0x45/0x56
Jun 14 19:31:36 desktop kernel:  [<ffffffff8103bbc8>] warn_slowpath_common+0x78/0xa0
Jun 14 19:31:36 desktop kernel:  [<ffffffff8103bca5>] warn_slowpath_null+0x15/0x20
Jun 14 19:31:36 desktop kernel:  [<ffffffffa030f3bc>] send_vblank_event+0xac/0x100 [drm]
Jun 14 19:31:36 desktop kernel:  [<ffffffffa030f483>] drm_send_vblank_event+0x73/0xb0 [drm]
Jun 14 19:31:36 desktop kernel:  [<ffffffffa0422543>] intel_crtc_page_flip+0x1b3/0x440 [i915]
Jun 14 19:31:36 desktop kernel:  [<ffffffffa031bf3f>] drm_mode_page_flip_ioctl+0x14f/0x300 [drm]
Jun 14 19:31:36 desktop kernel:  [<ffffffffa030b788>] drm_ioctl+0x1d8/0x5d0 [drm]
Jun 14 19:31:36 desktop kernel:  [<ffffffffa031bdf0>] ? drm_mode_gamma_get_ioctl+0xe0/0xe0 [drm]
Jun 14 19:31:36 desktop kernel:  [<ffffffff8105d505>] ? enqueue_hrtimer+0x25/0x80
Jun 14 19:31:36 desktop kernel:  [<ffffffff8105daae>] ? __hrtimer_start_range_ns+0x1de/0x390
Jun 14 19:31:36 desktop kernel:  [<ffffffff81138c28>] do_vfs_ioctl+0x2c8/0x4a0
Jun 14 19:31:36 desktop kernel:  [<ffffffff81359725>] ? __sys_recvmsg+0x65/0x80
Jun 14 19:31:36 desktop kernel:  [<ffffffff81138e81>] SyS_ioctl+0x81/0xa0
Jun 14 19:31:36 desktop kernel:  [<ffffffff814234a2>] system_call_fastpath+0x16/0x1b
Jun 14 19:31:36 desktop kernel: ---[ end trace fa34b035d305b8a8 ]---
Jun 14 19:31:37 desktop kernel: ------------[ cut here ]------------
Jun 14 19:31:37 desktop kernel: WARNING: CPU: 1 PID: 165 at drivers/gpu/drm/drm_irq.c:770 send_vblank_event+0xac/0x100 [drm]()
Jun 14 19:31:37 desktop kernel: Modules linked in: usbhid snd_hda_codec_realtek snd_hda_codec_generic coretemp hwmon kvm_intel kvm microcode pcspkr i2c_i801 uhci_hcd i915 cfbfillrect cfbimgblt snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep i2c_algo_bit snd_pcm cfbcopyarea drm_kms_helper snd_timer drm snd intel_agp intel_gtt ehci_pci ehci_hcd usbcore rtc_cmos agpgart evdev usb_common e1000e soundcore ipv6
Jun 14 19:31:37 desktop kernel: CPU: 1 PID: 165 Comm: Xorg Tainted: G        W     3.15.0-gentoo-r1-first #1
Jun 14 19:31:37 desktop kernel: Hardware name:                  /DQ35JO, BIOS JOQ3510J.86A.1143.2010.1209.0048 12/09/2010
Jun 14 19:31:37 desktop kernel:  0000000000000009 ffff880221877c58 ffffffff8141ce58 0000000000000000
Jun 14 19:31:37 desktop kernel:  ffff880221877c90 ffffffff8103bbc8 ffff8801ec811540 ffff88022199a000
Jun 14 19:31:37 desktop kernel:  ffff880203c1df00 ffff880221f9e000 ffff88022199a200 ffff880221877ca0
Jun 14 19:31:37 desktop kernel: Call Trace:
Jun 14 19:31:37 desktop kernel:  [<ffffffff8141ce58>] dump_stack+0x45/0x56
Jun 14 19:31:37 desktop kernel:  [<ffffffff8103bbc8>] warn_slowpath_common+0x78/0xa0
Jun 14 19:31:37 desktop kernel:  [<ffffffff8103bca5>] warn_slowpath_null+0x15/0x20
Jun 14 19:31:37 desktop kernel:  [<ffffffffa030f3bc>] send_vblank_event+0xac/0x100 [drm]
Jun 14 19:31:37 desktop kernel:  [<ffffffffa030f483>] drm_send_vblank_event+0x73/0xb0 [drm]
Jun 14 19:31:37 desktop kernel:  [<ffffffffa0422543>] intel_crtc_page_flip+0x1b3/0x440 [i915]
Jun 14 19:31:37 desktop kernel:  [<ffffffffa031bf3f>] drm_mode_page_flip_ioctl+0x14f/0x300 [drm]
Jun 14 19:31:37 desktop kernel:  [<ffffffffa030b788>] drm_ioctl+0x1d8/0x5d0 [drm]
Jun 14 19:31:37 desktop kernel:  [<ffffffffa031bdf0>] ? drm_mode_gamma_get_ioctl+0xe0/0xe0 [drm]
Jun 14 19:31:37 desktop kernel:  [<ffffffff8105d505>] ? enqueue_hrtimer+0x25/0x80
Jun 14 19:31:37 desktop kernel:  [<ffffffff8105daae>] ? __hrtimer_start_range_ns+0x1de/0x390
Jun 14 19:31:37 desktop kernel:  [<ffffffff81138c28>] do_vfs_ioctl+0x2c8/0x4a0
Jun 14 19:31:37 desktop kernel:  [<ffffffff81359725>] ? __sys_recvmsg+0x65/0x80
Jun 14 19:31:37 desktop kernel:  [<ffffffff81138e81>] SyS_ioctl+0x81/0xa0
Jun 14 19:31:37 desktop kernel:  [<ffffffff814234a2>] system_call_fastpath+0x16/0x1b
Jun 14 19:31:37 desktop kernel: ---[ end trace fa34b035d305b8a9 ]---
Jun 14 19:31:37 desktop gdm-Xorg-:0[165]: (II) AIGLX: Suspending AIGLX clients for VT switch
Comment 14 Imre Deak 2014-06-14 18:02:53 UTC 
Created attachment 101059 [details] [review]
fix error dump

(In reply to comment #12)
> Created attachment 101058 [details]
> /sys/class/drm/card0/error with kernel 3.15.0

This error report is still broken, but 3.15.0 doesn't have yet the fix. It's included in Linus' development branch, you can get it with:

git clone -b master git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

I also attached the fix, so I'd like to ask you to either apply it on 3.14.4 or just clone the above branch and send a new error report.

Thanks for your help.
Comment 15 Francesco Turco 2014-06-14 20:17:19 UTC 
Created attachment 101064 [details]
/sys/class/drm/card0/error with kernel from git

I cloned the git repository as you described. I hope the error log is good now.
Comment 16 Imre Deak 2014-06-14 21:16:17 UTC 
(In reply to comment #15)
> Created attachment 101064 [details]
> /sys/class/drm/card0/error with kernel from git
> 
> I cloned the git repository as you described. I hope the error log is good
> now.

Yes, it shows now the expected values (pipe power state is on). I'll send this fix to the stable team for inclusion in 3.14. Thanks for your effort!
Comment 17 Chris Wilson 2014-06-15 05:51:50 UTC 
(In reply to comment #15)
> Created attachment 101064 [details]
> /sys/class/drm/card0/error with kernel from git
> 
> I cloned the git repository as you described. I hope the error log is good
> now.

That's a different hang. It survived boot (where the original display fault occurs) and dies inside a mesa batchbuffer. You need to open a separate bug report against Mesa/i915 with that error state. As it looks like it dies early on in gnome-shell it is fairly critical!
Comment 18 Francesco Turco 2014-06-15 08:39:38 UTC 
OK, I just filed bug 80046.
Comment 19 Chris Wilson 2014-06-23 07:05:07 UTC 
*** Bug 80377 has been marked as a duplicate of this bug. ***
Comment 20 Chris Wilson 2014-06-23 07:05:38 UTC 
(In reply to comment #19)
> *** Bug 80377 has been marked as a duplicate of this bug. ***

Num Pipes: 2
Pipe [0]:
  Power: on
  SRC: 00000000
  STAT: 10000000
Plane [0]:
  CNTR: d9000000
  STRIDE: 00001000
  SIZE: 02ff03ff
  POS: 00000000
  ADDR: 00800000
Cursor [0]:
  CNTR: 00000000
  POS: 00000000
  BASE: 00000000
Pipe [1]:
  Power: on
  SRC: 03ff02ff
  STAT: 10020200
Plane [1]:
  CNTR: 00000000
  STRIDE: 00000000
  SIZE: 00000000
  POS: 00000000
  ADDR: 00000000
Cursor [1]:
  CNTR: 00000000
  POS: 00000000
  BASE: 00000000
CPU transcoder: A
  Power: on
  CONF: 00000000
  HTOTAL: 00000000
  HBLANK: 00000000
  HSYNC: 00000000
  VTOTAL: 00000000
  VBLANK: 00000000
  VSYNC: 00000000
CPU transcoder: B
  Power: on
  CONF: 80000000
  HTOTAL: 053f03ff
  HBLANK: 053f03ff
  HSYNC: 049f0417
  VTOTAL: 032502ff
  VBLANK: 032502ff
  VSYNC: 03080302
Comment 21 Priit Laes (irc: plaes) 2014-09-02 03:52:05 UTC 
Created attachment 105584 [details]
/sys/class/drm/card0/error-3.17.0-rc2+

Num Pipes: 2
Pipe [0]:
  Power: on
  SRC: 068f0419
  STAT: 10000203
Plane [0]:
  CNTR: d9000000
  STRIDE: 00002a40
  SIZE: 02ff03ff
  POS: 00000000
  ADDR: 06f10000
Cursor [0]:
  CNTR: 00000000
  POS: 028b803a
  BASE: 00000000
Pipe [1]:
  Power: on
  SRC: 03ff02ff
  STAT: 10000302
Plane [1]:
  CNTR: d8000000
  STRIDE: 00002a40
  SIZE: 0419068f
  POS: 00000000
  ADDR: 06f11000
Cursor [1]:
  CNTR: 14000027
  POS: 0213013e
  BASE: 05414000
CPU transcoder: A
  Power: on
  CONF: 80000000
  HTOTAL: 08bf068f
  HBLANK: 08bf068f
  HSYNC: 07a706f7
  VTOTAL: 04400419
  VBLANK: 04400419
  VSYNC: 0422041c
CPU transcoder: B
  Power: on
  CONF: 80000000
  HTOTAL: 053f03ff
  HBLANK: 053f03ff
  HSYNC: 049f0417
  VTOTAL: 032502ff
  VBLANK: 032502ff
  VSYNC: 03080302
lines 32847-32902/32902 (END)
Comment 22 Jani Nikula 2015-01-29 12:40:22 UTC 
Long time no updates, is this still an issue with recent kernels?
Comment 23 Francesco Turco 2015-01-29 17:45:18 UTC 
I cannot reproduce this bug anymore since I have changed my monitor and my Linux distribution (using Arch Linux now).
Comment 24 Jani Nikula 2015-01-30 06:34:23 UTC 
(In reply to Francesco Turco from comment #23)
> I cannot reproduce this bug anymore since I have changed my monitor and my
> Linux distribution (using Arch Linux now).

Okay, anyone else?
Comment 25 Ander Conselvan de Oliveira 2015-06-05 12:20:00 UTC 
(In reply to Jani Nikula from comment #24)
> (In reply to Francesco Turco from comment #23)
> > I cannot reproduce this bug anymore since I have changed my monitor and my
> > Linux distribution (using Arch Linux now).
> 
> Okay, anyone else?

Looks like no one reproduced this in a few months. Presuming it's fixed. Please reopen if that's not the case.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.