<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [regression] [bisected] i915 GPU HANG: ecode 7:1:0xfffffffe on Kernel 5.1.x and 5.2rc1 to 5.2rc6" href="https://bugs.freedesktop.org/show_bug.cgi?id=111014#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [regression] [bisected] i915 GPU HANG: ecode 7:1:0xfffffffe on Kernel 5.1.x and 5.2rc1 to 5.2rc6" href="https://bugs.freedesktop.org/show_bug.cgi?id=111014">bug 111014</a> from <a class="email" href="mailto:dirkneukirchen@web.de" title="dirkneukirchen@web.de">dirkneukirchen@web.de</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=111014#c17">comment #17</a>) > Waitasec, in upstream, we invalidate before the switch. Could you please > check with 5.2 to see if it is already fixed? it happens in 5.2rc1 to the latest 5.2-rc6 too - see the attached files of the dmesg output and the sysfs file i attached 5.1.12 (so after release), 5.1-rc1 of 5.1 series AND various 5.2-rcX messages/error sysfs files and a log+sysfs from the first bad commit I found during bisect PS: drivers/gpu/drm/i915/gt/intel_ringbuffer.c does not exist in Linux 5.2-rc6 so I cannot test that - and it does not seem to apply if i try to patch the i915/intel_ringbuffer.c that is there</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>