On Tue, May 21, 2019 at 06:37:30PM -0000, Patchwork wrote: > == Series Details == > > Series: series starting with [v5,1/2] drm/i915: Make sandybridge_pcode_read() deal with the second data register > URL : https://patchwork.freedesktop.org/series/60921/ > State : success > > == Summary == > > CI Bug Log - changes from CI_DRM_6114 -> Patchwork_13064 > ==================================================== > > Summary > ------- > > **SUCCESS** > > No regressions found. > > External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13064/ > > Possible new issues > ------------------- > > Here are the unknown changes that may have been introduced in Patchwork_13064: > > ### IGT changes ### > > #### Suppressed #### > > The following results come from untrusted machines, tests, or statuses. > They do not affect the overall result. > > * igt@i915_pm_rpm@module-reload: > - {fi-icl-y}: [PASS][1] -> [DMESG-WARN][2] +1 similar issue > [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/fi-icl-y/igt@i915_pm_rpm@xxxxxxxxxxxxxxxxxx > [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13064/fi-icl-y/igt@i915_pm_rpm@xxxxxxxxxxxxxxxxxx Sigh. Looks like pcode on this icl-y doesn't support the new commands to retrieve the memory subsystem information. BIOS update maybe could fix that? -- Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
