Bug 109480

Summary: [CI][DRMTIP] igt@kms_busy@extended-modeset-...-[abc] - incomplete - GEM_BUG_ON(engine->last_retired_context != to_intel_context(i915->kernel_context, engine))
Product: DRI Reporter: Martin Peres <martin.peres>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: high CC: intel-gfx-bugs
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: HSW, IVB, SNB i915 features: GEM/Other

Description Martin Peres 2019-01-28 13:33:01 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_201/fi-hsw-peppy/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a.html

<3> [300.457186] assert_kernel_context_is_current:3010 GEM_BUG_ON(engine->last_retired_context != to_intel_context(i915->kernel_context, engine))
<4> [300.457389] ------------[ cut here ]------------
<2> [300.457393] kernel BUG at drivers/gpu/drm/i915/i915_gem.c:3010!
<4> [300.457407] invalid opcode: 0000 [#1] PREEMPT SMP PTI
<4> [300.457413] CPU: 1 PID: 7 Comm: kworker/u4:0 Tainted: G     U            5.0.0-rc3-g310d38b4b51e-drmtip_201+ #1
<4> [300.457417] Hardware name: GOOGLE Peppy/Peppy, BIOS MrChromebox 02/04/2018
<4> [300.457493] Workqueue: i915 i915_gem_idle_work_handler [i915]
<4> [300.457557] RIP: 0010:assert_kernel_context_is_current.part.7+0xea/0xf0 [i915]
<4> [300.457562] Code: 85 a6 bf c2 48 8b 35 9d 72 1e 00 49 c7 c0 70 2d 67 c0 b9 c2 0b 00 00 48 c7 c2 e0 ec 63 c0 48 c7 c7 b5 e6 52 c0 e8 d6 3a c6 c2 <0f> 0b 0f 1f 40 00 48 8b 87 20 a5 00 00 48 85 c0 78 56 8b 87 40 b1
<4> [300.457566] RSP: 0018:ffffa879c0047e00 EFLAGS: 00010286
<4> [300.457571] RAX: 000000000000001e RBX: ffff976b9b6c7760 RCX: 0000000000000000
<4> [300.457575] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffff976bb46b8008
<4> [300.457578] RBP: ffff976baa0ea158 R08: 000000000000026d R09: ffff976bb460c000
<4> [300.457582] R10: 0000000000000000 R11: ffff976bb46b8008 R12: ffff976b9b6c0000
<4> [300.457586] R13: ffff976b9b6c77a0 R14: ffff976b9b6c0000 R15: 00000000ffffffff
<4> [300.457590] FS:  0000000000000000(0000) GS:ffff976c40100000(0000) knlGS:0000000000000000
<4> [300.457594] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [300.457598] CR2: 0000557d71f38960 CR3: 000000005ee36006 CR4: 00000000000606e0
<4> [300.457601] Call Trace:
<4> [300.457666]  i915_gem_idle_work_handler+0x1f7/0x280 [i915]
<4> [300.457676]  process_one_work+0x245/0x610
<4> [300.457685]  worker_thread+0x37/0x380
<4> [300.457691]  ? process_one_work+0x610/0x610
<4> [300.457698]  kthread+0x119/0x130
<4> [300.457704]  ? kthread_park+0x80/0x80
<4> [300.457712]  ret_from_fork+0x3a/0x50
<4> [300.457721] Modules linked in: snd_hda_codec_hdmi x86_pkg_temp_thermal coretemp crct10dif_pclmul crc32_pclmul cdc_ether usbnet ghash_clmulni_intel i2c_i801 r8152 mii i915 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core mei_me mei snd_pcm lpc_ich prime_numbers btusb btrtl btbcm btintel bluetooth ecdh_generic
<0> [300.457746] Dumping ftrace buffer:
<0> [300.472114] ---------------------------------
<4> [300.481655] ---[ end trace 9ad466c8cf375a48 ]---
Comment 1 CI Bug Log 2019-01-28 13:34:39 UTC 
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SNBm HSW IVBm: igt@kms_busy@extended-modeset-...-[abc] - incomplete - GEM_BUG_ON(engine-&gt;last_retired_context != to_intel_context(i915-&gt;kernel_context, engine))
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-hsw-peppy/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-c.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-hsw-peppy/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-b.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-hsw-peppy/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-ivb-3520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-c.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-ivb-3520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-b.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-ivb-3520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-snb-2520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-b.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-snb-2520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-hsw-peppy/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-c.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-hsw-peppy/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-b.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-hsw-peppy/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-ivb-3520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-c.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-ivb-3520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-b.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-ivb-3520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-snb-2520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-b.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-snb-2520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_201/fi-hsw-peppy/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-c.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_201/fi-hsw-peppy/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-b.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_201/fi-hsw-peppy/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_201/fi-ivb-3520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-c.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_201/fi-ivb-3520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-b.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_201/fi-ivb-3520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_201/fi-snb-2520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-b.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_201/fi-snb-2520m/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-a.html
Comment 2 Francesco Balestrieri 2019-02-12 15:18:29 UTC 
Happens very frequently in CI, raising to "high"
Comment 3 Chris Wilson 2019-02-12 17:12:12 UTC 
It's not a huge issue and is scheduled for deletion along with global_seqno.
Comment 4 Chris Wilson 2019-03-10 09:59:56 UTC 
If you remove the test, it cannot fail!

commit 7d6ce55887a44c15c6df29e883d0ea567c8ac55c
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Mar 8 09:36:57 2019 +0000

    drm/i915: Remove has-kernel-context
    
    We can no longer assume execution ordering, and in particular we cannot
    assume which context will execute last. One side-effect of this is that
    we cannot determine if the kernel-context is resident on the GPU, so
    remove the routines that claimed to do so.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20190308093657.8640-4-chris@chris-wilson.co.uk
Comment 5 Martin Peres 2019-03-13 15:48:23 UTC 
(In reply to Chris Wilson from comment #4)
> If you remove the test, it cannot fail!
> 
> commit 7d6ce55887a44c15c6df29e883d0ea567c8ac55c
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Fri Mar 8 09:36:57 2019 +0000
> 
>     drm/i915: Remove has-kernel-context
>     
>     We can no longer assume execution ordering, and in particular we cannot
>     assume which context will execute last. One side-effect of this is that
>     we cannot determine if the kernel-context is resident on the GPU, so
>     remove the routines that claimed to do so.
>     
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>     Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>     Link:
> https://patchwork.freedesktop.org/patch/msgid/20190308093657.8640-4-
> chris@chris-wilson.co.uk

Thanks, it indeed has not been seen since drmtip_240 (2 drmtip runs ago). Closing!
Comment 6 CI Bug Log 2019-03-13 15:48:33 UTC 
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.

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.