From: Krzysztof Kolasa <kkolasa@winsoft.pl>
To: daniel.vetter@intel.com, jani.nikula@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org, mika.kuoppala@intel.com
Subject: interference on display, Intel 945GM, 32bit system, kernel next
Date: Sun, 19 Jul 2015 20:07:19 +0200 [thread overview]
Message-ID: <55ABE757.2080005@winsoft.pl> (raw)
Photo laptop screen:
https://drive.google.com/open?id=0B1LAMAFWTdeweTJycjFoZkNSVmM
bisected first bad commit: [0875546c5318c85c13d07014af5350e9000bc9e9] drm/i915: Fix up the vma aliasing ppgtt binding
crash dump /sys/class/drm/card0/error :
GPU HANG: ecode 3:0:0x0063ffe6, in Xorg [1221], reason: Ring hung, action: reset
Time: 1437324820 s 168714 us
Kernel: 4.2.0-rc2-winsoft-x86+
Active process (on ring render): Xorg [1221]
Reset count: 0
Suspend count: 1
PCI ID: 0x27a2
EIR: 0x00000000
IER: 0x00020053
PGTBL_ER: 0x00000000
FORCEWAKE: 0x00000000
DERRMR: 0x00000000
CCID: 0x00000000
Missed interrupts: 0x00000000
fence[0] = 08b00021
fence[1] = 02800341
fence[2] = 04000331
fence[3] = 05000341
fence[4] = 08c00001
fence[5] = 08800011
fence[6] = 0a100001
fence[7] = 09f00011
fence[8] = 0a800341
fence[9] = 07000231
fence[10] = 03900001
fence[11] = 0a200001
fence[12] = 00000000
fence[13] = 00000000
fence[14] = 00000000
fence[15] = 02000341
INSTDONE_0: 0x7fffffc1
INSTDONE_1: 0x00000000
INSTDONE_2: 0x00000000
INSTDONE_3: 0x00000000
render command stream:
START: 0x00000000
HEAD: 0x00a13778
TAIL: 0x000137e0
CTL: 0x0001f001
HWS: 0x00000000
ACTHD: 0x00000000 090088cc
IPEIR: 0x00000000
IPEHR: 0x7f9c0027
INSTDONE: 0x7fffffc1
INSTPM: 0x00000800
FADDR: 0x00000000 090090c0
seqno: 0x000477e8
waiting: yes
ring->head: 0x0001fe88
ring->tail: 0x000137e0
hangcheck: hung [40]
vm[0]
Active [17]:
09004000 20480 7e 00 [ 477e9 00 00 00 00 ] 00 dirty uncached
08a4c000 4096 7e 00 [ 477ea 00 00 00 00 ] 00 dirty uncached
05000000 7340032 36 00 [ 477ea 00 00 00 00 ] 477ea X dirty render uncached (fence: 3)
02800000 6553600 36 00 [ 477ea 00 00 00 00 ] 477ea X dirty render uncached (name: 3) (fence: 1)
06000000 7340032 37 00 [ 477ea 00 00 00 00 ] 00 X uncached
08a44000 32768 76 00 [ 477ea 00 00 00 00 ] 00 dirty uncached
06800000 6553600 37 00 [ 477ea 00 00 00 00 ] 00 X uncached (name: 7)
08800000 655360 36 00 [ 477ea 00 00 00 00 ] 00 X dirty uncached (name: 8) (fence: 5)
03000000 6553600 37 00 [ 477ea 00 00 00 00 ] 00 X uncached (name: 10)
0b000000 4096 37 00 [ 477ea 00 00 00 00 ] 00 uncached
06f00000 786432 37 00 [ 477ea 00 00 00 00 ] 00 X uncached
07a00000 4096 7e 00 [ 477eb 00 00 00 00 ] 00 dirty uncached
04000000 6553600 02 00 [ 477eb 00 00 00 00 ] 477eb X dirty render uncached (name: 9) (fence: 2)
07000000 2654208 02 00 [ 477eb 00 00 00 00 ] 477eb X dirty render uncached (fence: 9)
07c00000 4194304 37 00 [ 477eb 00 00 00 00 ] 00 Y uncached
03a00000 262144 06 00 [ 477eb 00 00 00 00 ] 477eb Y dirty render uncached
08a04000 262144 76 00 [ 477eb 00 00 00 00 ] 00 dirty uncached
Pinned [3]:
00000000 131072 40 40 [ 00 00 00 00 00 ] 00 P dirty uncached
00020000 4096000 40 00 [ 00 00 00 00 00 ] 00 P dirty uncached (name: 1)
02000000 6553600 02 00 [ 00 00 00 00 00 ] 00 P X dirty uncached (name: 4) (fence: 15)
render ring (submitted by Xorg [1221]) --- gtt_offset = 0x09004000
00000000 : 6ba008a1
00000004 : 76fac688
00000008 : 7d040783
0000000c : 00000000
00000010 : 009020c0
00000014 : 00000000
<<<<<<<<<<<<<<<<<<....................................... ( cut section of the file )
00004fe0 : 00000000
00004fe4 : 00000000
00004fe8 : 00000000
00004fec : 00000000
00004ff0 : 00000000
00004ff4 : 00000000
00004ff8 : 00000000
00004ffc : 00000000
render ring --- 3 requests
seqno 0x000477e9, emitted 526211, tail 0x00013780
seqno 0x000477ea, emitted 526212, tail 0x000137a8
seqno 0x000477eb, emitted 526212, tail 0x000137d0
render ring --- ringbuffer = 0x00000000
00000000 : 02000001
00000004 : 00000000
00000008 : 18800080
0000000c : 037c0001
00000010 : 02000000
00000014 : 00000000
00000018 : 10800001
0000001c : 000000c0
00000020 : 00047020
<<<<<<<<<<<<<<<<<<...................................... ( cut section of the file )
0001ffdc : 00000000
0001ffe0 : 18800080
0001ffe4 : 037c0001
0001ffe8 : 02000000
0001ffec : 00000000
0001fff0 : 10800001
0001fff4 : 000000c0
0001fff8 : 0004701f
0001fffc : 01000000
Num Pipes: 2
Pipe [0]:
Power: on
SRC: 00000000
STAT: 10000000
Plane [0]:
CNTR: d9000000
STRIDE: 00002000
SIZE: 031f04ff
POS: 00000000
ADDR: 02000000
Cursor [0]:
CNTR: 00000000
POS: 00000000
BASE: 00000000
Pipe [1]:
Power: on
SRC: 04ff031f
STAT: 10000202
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: 057f04ff
HBLANK: 057f04ff
HSYNC: 05340514
VTOTAL: 032f031f
VBLANK: 032f031f
VSYNC: 03270323
------------------------------------------
kernel log:
ul 19 18:53:40 AMILO-V3405 kernel: [ 2408.992093] [drm] stuck on render ring
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2408.993832] [drm] GPU HANG: ecode 3:0:0x0063ffe6, in Xorg [1221], reason: Ring hung, action: reset
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2408.993837] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2408.993840] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2408.993844] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2408.993847] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2408.993850] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2408.993872] kobject: 'card0' (f4d34a08): kobject_uevent_env
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2408.993883] kobject: 'card0' (f4d34a08): fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/drm/card0'
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2408.993951] kobject: 'card0' (f4d34a08): kobject_uevent_env
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2408.993959] kobject: 'card0' (f4d34a08): fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/drm/card0'
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2409.449556] drm/i915: Resetting chip after gpu hang
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2409.802227] kobject: 'card0' (f4d34a08): kobject_uevent_env
Jul 19 18:53:40 AMILO-V3405 kernel: [ 2409.802243] kobject: 'card0' (f4d34a08): fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/drm/card0'
Jul 19 18:53:49 AMILO-V3405 systemd[1]: Started Session c4 of user krzysiek.
Jul 19 18:53:49 AMILO-V3405 systemd[1]: Starting Session c4 of user krzysiek.
Jul 19 18:54:52 AMILO-V3405 kernel: [ 2481.446128] IQK:Start!!!
Jul 19 18:54:52 AMILO-V3405 kernel: [ 2481.457252] Path A IQK Success!!
Jul 19 18:54:52 AMILO-V3405 kernel: [ 2481.465129] Path A IQK Success!!
Jul 19 18:54:52 AMILO-V3405 kernel: [ 2481.469895] IQK: final_candidate is 0
Jul 19 18:54:52 AMILO-V3405 kernel: [ 2481.469902] IQK: RegE94=105 RegE9C=b RegEA4=fb RegEAC=6 RegEB4=0 RegEBC=0 RegEC4=0 RegECC=0
Jul 19 18:54:52 AMILO-V3405 kernel: [ 2481.469902] Path A IQ Calibration Success !
Jul 19 18:51:48 AMILO-V3405 gnome-session[1863]: message repeated 6 times: [ (gnome-shell:1962): mutter-WARNING **: STACK_OP_RAISE_ABOVE: window 0x5b01a00019 not in stack]
Jul 19 19:00:28 AMILO-V3405 gnome-session[1863]: (gnome-screensaver:2048): GLib-CRITICAL **: Source ID 46 was not found when attempting to remove it
Jul 19 19:00:32 AMILO-V3405 kernel: [ 2820.832165] kobject: 'card0' (f4d34a08): kobject_uevent_env
Jul 19 19:00:32 AMILO-V3405 kernel: [ 2820.832187] kobject: 'card0' (f4d34a08): fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/drm/card0'
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2837.992184] [drm] stuck on render ring
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2837.993868] [drm] GPU HANG: ecode 3:0:0x7affffc1, in Xorg [1221], reason: Ring hung, action: reset
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2837.993891] i915: render error detected, EIR: 0x00000010
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2837.994019] i915: page table error
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2838.002100] i915: PGTBL_ER: 0x00200000
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2838.010328] [drm:i915_handle_error [i915]] *ERROR* EIR stuck: 0x00000010, masking
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2838.018292] kobject: 'card0' (f4d34a08): kobject_uevent_env
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2838.018980] kobject: 'card0' (f4d34a08): fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/drm/card0'
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2838.019799] kobject: 'card0' (f4d34a08): kobject_uevent_env
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2838.019812] kobject: 'card0' (f4d34a08): fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/drm/card0'
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2838.065113] drm/i915: Resetting chip after gpu hang
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2838.416909] kobject: 'card0' (f4d34a08): kobject_uevent_env
Jul 19 19:00:49 AMILO-V3405 kernel: [ 2838.416932] kobject: 'card0' (f4d34a08): fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/drm/card0'
---------------------------------------------
Krzysztof
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-07-19 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 18:07 Krzysztof Kolasa [this message]
2015-07-21 7:30 ` interference on display, Intel 945GM, 32bit system, kernel next Daniel Vetter
[not found] ` <55ADFDF0.4060407@winsoft.pl>
2015-07-21 8:41 ` Daniel Vetter
2015-07-21 8:58 ` Krzysztof Kolasa
2015-07-21 9:07 ` Daniel Vetter
2015-07-21 9:43 ` Chris Wilson
2015-07-21 12:48 ` Krzysztof Kolasa
2015-07-21 14:03 ` Daniel Vetter
2015-07-21 18:07 ` Krzysztof Kolasa
2015-07-22 8:27 ` Daniel Vetter
2015-07-22 9:38 ` Krzysztof Kolasa
2015-07-31 14:11 ` Krzysztof Kolasa
2015-07-31 14:54 ` Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55ABE757.2080005@winsoft.pl \
--to=kkolasa@winsoft.pl \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=mika.kuoppala@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.