Bug 109745

Summary:	[CI][SHARDS] igt@i915_suspend@debugfs-reader - dmesg-warn - i915_dsc_fec_support_show
Product:	DRI	Reporter:	Lakshmi <lakshminarayana.vudum>
Component:	DRM/Intel	Assignee:	Vanshidhar Konda <vanshidhar.r.konda>
Status:	RESOLVED FIXED	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	high	CC:	intel-gfx-bugs
Version:	DRI git
Hardware:	Other
OS:	All
Whiteboard:	ReadyForDev
i915 platform:	ICL	i915 features:	display/Other

Description Lakshmi 2019-02-22 14:56:02 UTC

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4850/shard-iclb3/igt@i915_suspend@debugfs-reader.html

<4> [1601.870376] WARNING: CPU: 3 PID: 8445 at drivers/gpu/drm/drm_modeset_lock.c:228 drm_modeset_drop_locks+0x35/0x40
<4> [1601.870427] RIP: 0010:drm_modeset_drop_locks+0x35/0x40
<4> [1601.870505]  i915_dsc_fec_support_show+0x91/0x190 [i915]
<4> [1601.870616] WARNING: CPU: 3 PID: 8445 at drivers/gpu/drm/drm_modeset_lock.c:228 drm_modeset_drop_locks+0x35/0x40

Comment 1 CI Bug Log 2019-02-22 14:57:28 UTC

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL: igt@i915_suspend@debugfs-reader - dmesg-warn - i915_dsc_fec_support_show
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4850/shard-iclb3/igt@i915_suspend@debugfs-reader.html

Comment 2 CI Bug Log 2019-02-22 14:59:47 UTC

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL: igt@runner@aborted - fail - Previous test: i915_suspend (debugfs-reader)
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4850/shard-iclb3/igt@runner@aborted.html

Comment 3 Lakshmi 2019-03-29 13:11:59 UTC

Vanshidhar, Any updates here?

Comment 4 Vanshidhar Konda 2019-03-29 16:22:45 UTC

(In reply to Lakshmi from comment #3)
> Vanshidhar, Any updates here?

Hello Lakshmi, this issue has not reproduced in > 30 days. I would suggest closing it.

Comment 5 Chris Wilson 2019-03-29 23:02:29 UTC

commit ee6df5694a9a2e30566ae05e9c145a0f6d5e087f (HEAD -> drm-intel-next-queued, 
drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Mar 29 16:51:52 2019 +0000

    drm/i915: Always backoff after a drm_modeset_lock() deadlock
    
    If drm_modeset_lock() reports a deadlock it sets the ctx->contexted
    field and insists that the caller calls drm_modeset_backoff() or else it
    generates a WARN on cleanup.

Comment 6 Martin Peres 2019-04-17 14:33:56 UTC

(In reply to Chris Wilson from comment #5)
> commit ee6df5694a9a2e30566ae05e9c145a0f6d5e087f (HEAD ->
> drm-intel-next-queued, 
> drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Fri Mar 29 16:51:52 2019 +0000
> 
>     drm/i915: Always backoff after a drm_modeset_lock() deadlock
>     
>     If drm_modeset_lock() reports a deadlock it sets the ctx->contexted
>     field and insists that the caller calls drm_modeset_backoff() or else it
>     generates a WARN on cleanup.

Thanks!

(In reply to Vanshidhar Konda from comment #4)
> (In reply to Lakshmi from comment #3)
> > Vanshidhar, Any updates here?
> 
> Hello Lakshmi, this issue has not reproduced in > 30 days. I would suggest
> closing it.

This is why looking at the reproduction rate is bad ;) The issue is real, just improbable. Next time, please investigate the logs more thoroughly and understand what the failure means ;)

Comment 7 CI Bug Log 2019-04-17 14:34:05 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.