[Bug 110275] [CI][SHARDS] igt at kms_flip@flip-vs-fences-interruptible - dmesg-warn- BUG: unable to handle kernel paging request

[bugzilla-daemon at freedesktop.org]

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

Martin Peres <martin.peres at free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|high                        |highest
      i915 features|                            |GEM/Other

--- Comment #6 from Martin Peres <martin.peres at free.fr> ---
(In reply to CI Bug Log from comment #4)
> A CI Bug Log filter associated to this bug has been updated:
> 
> {- ICL: igt at kms_flip@flip-vs-fences-interruptible - dmesg-warn- (BUG: unable
> to handle kernel paging request|general protection fault: 0000) -}
> {+ ICL: igt at kms_flip@flip-vs-fences-interruptible / 
> igt at gem_create@create-clear - dmesg-warn- (BUG: unable to handle kernel
> paging request|general protection fault: 0000) +}
> 
>  No new failures caught with the new filter

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5816/shard-iclb8/igt@gem_create@create-clear.html

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5808/shard-iclb6/igt@gem_create@create-clear.html

Since the test igt at kms_flip@flip-vs-fences-interruptible is using execbuf and
GTT fences, and we also fail at igt at gem_create@create-clear, there is a chance
that this is not a Linux issue, but instead a GEM one.

Given that this issue happened 4 times in a week on 4 different machines and
that the outcome of this issue is a oops, which breaks the users' machines
until they reboot, it is fair to increase the priority to highest.

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