Bug 109467 - [CI][SHARDS] igt@gem_eio@in-flight-* - dmesg-warn / dmesg-fail - include/linux/dma-fence.h:511 i915_reset_request
Summary: [CI][SHARDS] igt@gem_eio@in-flight-* - dmesg-warn / dmesg-fail - include/linu...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-28 09:05 UTC by Martin Peres
Modified: 2019-03-06 18:39 UTC (History)
1 user (show)

See Also:
i915 platform: BXT, CFL, CNL, GLK, ICL, KBL, SKL
i915 features: GEM/Other


Attachments

Description Martin Peres 2019-01-28 09:05:15 UTC
<7> [97.329038] [drm:i915_reset_device [i915]] resetting chip
<4> [97.329246] WARNING: CPU: 5 PID: 2703 at ./include/linux/dma-fence.h:511 i915_reset_request+0x268/0x350 [i915]
<4> [97.329248] Modules linked in: vgem snd_hda_codec_realtek snd_hda_codec_generic amdgpu x86_pkg_temp_thermal coretemp i915 btusb crct10dif_pclmul btrtl crc32_pclmul btbcm btintel snd_hda_codec_hdmi ghash_clmulni_intel bluetooth snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core chash ecdh_generic gpu_sched e1000e igb i2c_i801 snd_pcm ttm mei_me mei prime_numbers pinctrl_sunrisepoint pinctrl_intel
<4> [97.329287] CPU: 5 PID: 2703 Comm: gem_eio Tainted: G U 5.0.0-rc3-gf13eede6ea3e-drmtip_199+ #1
<4> [97.329289] Hardware name: Intel Corporation NUC8i7HVK/NUC8i7HVB, BIOS HNKBLi70.86A.0047.2018.0718.1706 07/18/2018
<4> [97.329314] RIP: 0010:i915_reset_request+0x268/0x350 [i915]
<4> [97.329316] Code: e8 6d bf 06 00 48 8b 83 a0 02 00 00 48 39 c5 48 8d 98 60 fd ff ff 75 e2 5b 4c 89 e7 5d 41 5c 41 5d 41 5e 41 5f e9 d8 47 3a dc <0f> 0b e9 eb fd ff ff 8b 8d 90 02 00 00 48 8b 55 20 45 89 e0 48 c7
<4> [97.329319] RSP: 0018:ffffab87802efa80 EFLAGS: 00010002
<4> [97.329321] RAX: 0000000000000003 RBX: ffff97242842f0c0 RCX: 0000000000000001
<4> [97.329323] RDX: 0000000080000001 RSI: 00000000ffffffff RDI: ffff97241f39a1b0
<4> [97.329326] RBP: 0000000000000000 R08: 000000000004e3c9 R09: ffff9724353b1000
<4> [97.329328] R10: ffffab87802ef9c0 R11: 0000000000000000 R12: 0000000000000000
<4> [97.329330] R13: ffff97241f39a198 R14: 0000000000000246 R15: 0000000000000000
<4> [97.329332] FS: 00007ff7d1c4f980(0000) GS:ffff972436b40000(0000) knlGS:0000000000000000
<4> [97.329334] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [97.329336] CR2: 00007ff7d1c84000 CR3: 00000002617ac004 CR4: 00000000003606e0
<4> [97.329338] Call Trace:
<4> [97.329372] execlists_reset+0xb2/0x160 [i915]
<4> [97.329390] ? i915_gem_unset_wedged.part.5+0x5c/0x340 [i915]
<4> [97.329413] intel_engines_sanitize+0x50/0x70 [i915]
<4> [97.329439] i915_gem_unset_wedged.part.5+0x19c/0x340 [i915]
<4> [97.329481] i915_reset+0xa2/0x3b0 [i915]
<4> [97.329500] i915_reset_device+0xd5/0x150 [i915]
<4> [97.329519] ? i915_gem_set_wedged+0x240/0x240 [i915]
<4> [97.329523] ? work_on_cpu_safe+0x50/0x50
<4> [97.329543] i915_handle_error+0x22a/0x360 [i915]
<4> [97.329551] ? perf_callchain_user+0x1b6/0x230
<4> [97.329609] i915_wedged_set+0x25/0x30 [i915]
<4> [97.329613] simple_attr_write+0xb0/0xd0
<4> [97.329617] full_proxy_write+0x51/0x80
<4> [97.329621] __vfs_write+0x31/0x190
<4> [97.329625] ? rcu_read_lock_sched_held+0x6f/0x80
<4> [97.329626] ? rcu_sync_lockdep_assert+0x29/0x50
<4> [97.329628] ? __sb_start_write+0x152/0x1f0
<4> [97.329630] ? __sb_start_write+0x163/0x1f0
<4> [97.329633] vfs_write+0xbd/0x1b0
<4> [97.329637] ksys_write+0x50/0xc0
<4> [97.329640] do_syscall_64+0x55/0x190
<4> [97.329644] entry_SYSCALL_64_after_hwframe+0x49/0xbe
<4> [97.329646] RIP: 0033:0x7ff7d11c4281
<4> [97.329647] Code: c3 0f 1f 84 00 00 00 00 00 48 8b 05 59 8d 20 00 c3 0f 1f 84 00 00 00 00 00 8b 05 8a d1 20 00 85 c0 75 16 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 89 d4 53
<4> [97.329649] RSP: 002b:00007ffd6ebfaf58 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
<4> [97.329651] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff7d11c4281
<4> [97.329652] RDX: 0000000000000002 RSI: 00007ff7d1847a26 RDI: 0000000000000009
<4> [97.329653] RBP: 00007ffd6ebfaf80 R08: 0000000000000000 R09: 0000000000000034
<4> [97.329655] R10: 0000000000000000 R11: 0000000000000246 R12: 000055f35e7e7c50
<4> [97.329656] R13: 00007ffd6ebfb7e0 R14: 0000000000000000 R15: 0000000000000000
<4> [97.329662] irq event stamp: 50018
<4> [97.329664] hardirqs last enabled at (50017): [<ffffffff9c9a089c>] _raw_spin_unlock_irqrestore+0x4c/0x60
<4> [97.329667] hardirqs last disabled at (50018): [<ffffffff9c9a070d>] _raw_spin_lock_irqsave+0xd/0x50
<4> [97.329669] softirqs last enabled at (49974): [<ffffffff9c836b7c>] peernet2id+0x4c/0x70
<4> [97.329671] softirqs last disabled at (49972): [<ffffffff9c836b5d>] peernet2id+0x2d/0x70
<4> [97.329687] WARNING: CPU: 5 PID: 2703 at ./include/linux/dma-fence.h:511 i915_reset_request+0x268/0x350 [i915]
<4> [97.329688] ---[ end trace 8ed401210f98adfb ]---
<5> [97.329730] i915 0000:00:02.0: Resetting chip for Manually set wedged engine mask = ffffffffffffffff
<6> [97.331665] [IGT] gem_eio: exiting, ret=0
Comment 1 Chris Wilson 2019-01-28 09:07:40 UTC
C'est la vie. Will be fixed up after flipping the switch for context seqno.
Comment 3 Chris Wilson 2019-01-29 08:21:41 UTC
Just a nuisance warn,

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
Comment 4 Martin Peres 2019-03-06 18:38:58 UTC
(In reply to Chris Wilson from comment #3)
> Just a nuisance warn,
> 
> 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

Looks good, thanks!
Comment 5 CI Bug Log 2019-03-06 18:39:09 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.