| Summary: | [CI][DRMTIP] igt@gem_eio@ - dmesg-fail / incomplete - GEM_BUG_ON(!i915_request_completed(request)) | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Martin Peres <martin.peres> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | BYT, HSW, IVB, SNB | i915 features: | GEM/Other |
|
Description
Martin Peres
2019-01-28 13:46:42 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-hsw-peppy/igt@gem_eio@reset-stress.html <3> [246.910194] i915_request_retire:255 GEM_BUG_ON(!i915_request_completed(request)) <4> [246.910477] ------------[ cut here ]------------ <2> [246.910481] kernel BUG at drivers/gpu/drm/i915/i915_request.c:255! <4> [246.910524] invalid opcode: 0000 [#1] PREEMPT SMP PTI <4> [246.910538] CPU: 1 PID: 954 Comm: kworker/u4:21 Tainted: G U 5.0.0-rc3-g08f37be937e0-drmtip_200+ #1 <4> [246.910556] Hardware name: GOOGLE Peppy/Peppy, BIOS MrChromebox 02/04/2018 <4> [246.910632] Workqueue: i915 restart_work [i915] <4> [246.910711] RIP: 0010:i915_request_retire+0x690/0x930 [i915] <4> [246.910724] Code: ef 85 ed eb 48 8b 35 27 ca 1c 00 49 c7 c0 d8 d6 37 c0 b9 ff 00 00 00 48 c7 c2 00 6b 34 c0 48 c7 c7 4b 07 25 c0 e8 40 1a f4 eb <0f> 0b 49 8b 57 28 49 8b 47 30 48 89 42 08 48 89 10 e9 4c ff ff ff <4> [246.910754] RSP: 0018:ffffb314808e7d50 EFLAGS: 00010282 <4> [246.910766] RAX: 000000000000000f RBX: ffff8b0ce33944c0 RCX: 0000000000000000 <4> [246.910780] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffff8b0cf46b8008 <4> [246.910793] RBP: ffffb314808e7d80 R08: 000000000011bc32 R09: ffff8b0cf460b000 <4> [246.910807] R10: 0000000000000000 R11: ffff8b0cf46b8008 R12: ffff8b0cd5e78f38 <4> [246.910820] R13: ffff8b0ce3396d40 R14: ffff8b0ce3394dc0 R15: ffff8b0cd5e78f50 <4> [246.910834] FS: 0000000000000000(0000) GS:ffff8b0d80100000(0000) knlGS:0000000000000000 <4> [246.910850] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 <4> [246.910862] CR2: 00007ffe09f7b598 CR3: 0000000068aca005 CR4: 00000000000606e0 <4> [246.910875] Call Trace: <4> [246.910888] ? rcu_read_lock_sched_held+0x6f/0x80 <4> [246.910968] i915_request_retire_upto+0xfd/0x150 [i915] <4> [246.911045] i915_request_add+0x3b0/0x7f0 [i915] <4> [246.911109] restart_work+0x7b/0xb0 [i915] <4> [246.911125] process_one_work+0x245/0x610 <4> [246.911140] worker_thread+0x37/0x380 <4> [246.911152] ? process_one_work+0x610/0x610 <4> [246.911164] kthread+0x119/0x130 <4> [246.911175] ? kthread_park+0x80/0x80 <4> [246.911189] ret_from_fork+0x3a/0x50 <4> [246.911202] Modules linked in: vgem snd_hda_codec_hdmi x86_pkg_temp_thermal coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cdc_ether usbnet r8152 mii i2c_i801 lpc_ich i915 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core snd_pcm mei_me mei prime_numbers btusb btrtl btbcm btintel bluetooth ecdh_generic The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BYT HSW SNBm: igt@gem_eio@ - dmesg-fail / incomplete - GEM_BUG_ON(!i915_request_completed(request)) - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-hsw-4770/igt@gem_eio@reset-stress.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-hsw-peppy/igt@gem_eio@reset-stress.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_199/fi-snb-2520m/igt@gem_eio@reset-stress.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-byt-n2820/igt@gem_eio@in-flight-contexts-10ms.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-hsw-peppy/igt@gem_eio@reset-stress.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_201/fi-hsw-peppy/igt@gem_eio@reset-stress.html I think this should have been cleared up by commit 5013eb8cd601c31e6d7d1b9d3291b24e933b77b2 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Jan 28 18:18:11 2019 +0000 drm/i915: Track the context's seqno in its own timeline HWSP A CI Bug Log filter associated to this bug has been updated:
{- BYT HSW SNBm: igt@gem_eio@ - dmesg-fail / incomplete - GEM_BUG_ON(!i915_request_completed(request)) -}
{+ BYT HSW SNBm: igt@gem_eio@ - dmesg-fail / incomplete - GEM_BUG_ON(!i915_request_completed(request)) +}
New failures caught by the filter:
* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_200/fi-snb-2520m/igt@gem_eio@reset-stress.html
A CI Bug Log filter associated to this bug has been updated:
{- BYT HSW SNBm: igt@gem_eio@ - dmesg-fail / incomplete - GEM_BUG_ON(!i915_request_completed(request)) -}
{+ BYT HSW SNBm: igt@gem_eio@ - dmesg-fail / incomplete - GEM_BUG_ON(!i915_request_completed(request)) +}
New failures caught by the filter:
* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_202/fi-ivb-3520m/igt@gem_eio@reset-stress.html
(In reply to Chris Wilson from comment #3) > I think this should have been cleared up by > > commit 5013eb8cd601c31e6d7d1b9d3291b24e933b77b2 > Author: Chris Wilson <chris@chris-wilson.co.uk> > Date: Mon Jan 28 18:18:11 2019 +0000 > > drm/i915: Track the context's seqno in its own timeline HWSP Does not seem like it. here are the last 3 failures: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_225/fi-ivb-3520m/igt@gem_eio@reset-stress.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_230/fi-ivb-3520m/igt@gem_eio@reset-stress.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_232/fi-byt-j1900/igt@gem_eio@reset-stress.html (In reply to Martin Peres from comment #6) > (In reply to Chris Wilson from comment #3) > > I think this should have been cleared up by > > > > commit 5013eb8cd601c31e6d7d1b9d3291b24e933b77b2 > > Author: Chris Wilson <chris@chris-wilson.co.uk> > > Date: Mon Jan 28 18:18:11 2019 +0000 > > > > drm/i915: Track the context's seqno in its own timeline HWSP > > Does not seem like it. here are the last 3 failures: > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_225/fi-ivb-3520m/ > igt@gem_eio@reset-stress.html > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_230/fi-ivb-3520m/ > igt@gem_eio@reset-stress.html > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_232/fi-byt-j1900/ > igt@gem_eio@reset-stress.html Which is not the same bug. And we have #109723 for that variant. (In reply to Chris Wilson from comment #7) > (In reply to Martin Peres from comment #6) > > (In reply to Chris Wilson from comment #3) > > > I think this should have been cleared up by > > > > > > commit 5013eb8cd601c31e6d7d1b9d3291b24e933b77b2 > > > Author: Chris Wilson <chris@chris-wilson.co.uk> > > > Date: Mon Jan 28 18:18:11 2019 +0000 > > > > > > drm/i915: Track the context's seqno in its own timeline HWSP > > > > Does not seem like it. here are the last 3 failures: > > > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_225/fi-ivb-3520m/ > > igt@gem_eio@reset-stress.html > > > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_230/fi-ivb-3520m/ > > igt@gem_eio@reset-stress.html > > > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_232/fi-byt-j1900/ > > igt@gem_eio@reset-stress.html > > Which is not the same bug. And we have #109723 for that variant. OK, closing this bug! Thanks! 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.