<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [GM45] i915: render error detected - Invalid GTT entry during fetch for host" href="https://bugs.freedesktop.org/show_bug.cgi?id=53385#c47">Comment # 47</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [GM45] i915: render error detected - Invalid GTT entry during fetch for host" href="https://bugs.freedesktop.org/show_bug.cgi?id=53385">bug 53385</a> from <a class="email" href="mailto:andreas.sturmlechner@gmail.com" title="andreas.sturmlechner@gmail.com">andreas.sturmlechner@gmail.com</a> <pre>(In reply to <a href="show_bug.cgi?id=53385#c46">comment #46</a>) > Andreas, what's the situation with current drm-intel-nightly? I just tried the latest state of drm-intel-nightly on the setup that's troubled by <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - false positives in grammar checking (Lightproof–Hunspell synchronization/cache problem)" href="show_bug.cgi?id=57461">bug 57461</a> and <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [DP] Getting kernel WARN every time I disconnect a DisplayPort monitor" href="show_bug.cgi?id=69251">bug 69251</a> (external display via DisplayPort), and it's got a bit worse: 1.) System freezes every time that - presumably - EDID is accessed. At first there's a noticeable black screen delay between grub2 and init, then it proceeds fine to the login manager, all seems fine at that point. 2.) That 5-6 seconds freeze (total lock, any input is lost) then happens each time I switch between fbcon and login manager, and doing that I can soon provoke the following error in dmesg: [ 66.836072] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 3.) Starting the desktop environment results in a multitude of those freezes, presumably because KDE tries to detect and find out a few things about display capabilities, color management and whatnot, startup is considerably delayed by that. 4.) How to reproduce the freeze: ~ $ time oyranos-monitor -l 0: ":0.0" 1920,00x1200,00+0,00+0,00 S2243W real 0m6.230s user 0m0.034s sys 0m0.033s 5.) During first startup of the new kernel image I also got an 'hpd interrupt storm' in dmesg, a few restarts later a familiar error has reappeared: [ 457.189291] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 457.189296] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 457.189297] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 457.189299] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 457.189300] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 457.190004] i915: render error detected, EIR: 0x00000010 [ 457.190004] i915: IPEIR: 0x00000000 [ 457.190004] i915: IPEHR: 0x54c00006 [ 457.190004] i915: INSTDONE_0: 0x808f837f [ 457.190004] i915: INSTDONE_1: 0xbf2706ae [ 457.190004] i915: INSTDONE_2: 0x00000000 [ 457.190004] i915: INSTDONE_3: 0x00000000 [ 457.190004] i915: INSTPS: 0x8001e025 [ 457.190004] i915: ACTHD: 0x01bcb45c [ 457.190004] i915: page table error [ 457.190004] i915: PGTBL_ER: 0x00000001 [ 457.190004] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>