Re: ✗ Fi.CI.BAT: failure for Resolve suspend-resume racing with GuC destroy-context-worker (rev8)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2023-12-01 at 02:20 +0000, Patchwork wrote:
> Patch Details
> Series: Resolve suspend-resume racing with GuC destroy-context-worker (rev8)
> URL:    https://patchwork.freedesktop.org/series/121916/
> State:  failure
> Details:        https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_121916v8/index.html

alan:snip
> Here are the unknown changes that may have been introduced in Patchwork_121916v8:
> 
> IGT changes
> Possible regressions
> 
>   *   igt@i915_selftest@live@requests:
>      *   bat-mtlp-6: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13956/bat-mtlp-6/igt@i915_selftest@live@xxxxxxxxxxxxx> -> DMESG-FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_121916v8/bat-mtlp-6/igt@i915_selftest@live@xxxxxxxxxxxxx>
alan: inspecting the selftest code that is failing WRT changes in this targets, i really dont see any relation.
the series is changing how we handle context deregistratoin either thru the regular context-close or through the
flushing during suspend... however the selftest reporting a reset would be an issue where the context is not
closed (because it would be hanging) - also its a kernel context - which should not get closed. 
I will run another retest after i verify trybot sees no issue.




[Index of Archives]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux