[Bug 90994] [BDW regression] pm_rpm subtests fail and give WARNs
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Jun 17 01:17:31 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=90994
--- Comment #1 from lu hua <huax.lu at intel.com> ---
I also see following case fail:
igt at pm_rpm@cursor-dpms
igt at pm_rpm@dpms-lpsp
igt at pm_rpm@dpms-mode-unset-lpsp
igt at pm_rpm@dpms-non-lpsp
igt at pm_rpm@drm-resources-equal
igt at pm_rpm@fences-dpms
igt at pm_rpm@gem-evict-pwrite
igt at pm_rpm@legacy-planes-dpms
igt at pm_rpm@universal-planes-dpms
Bisect shows: 7f072451f2d3d53e4f6939440e15ab36afed2051 is the first bad commit.
commit 7f072451f2d3d53e4f6939440e15ab36afed2051
Author: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
AuthorDate: Mon Jun 1 12:50:04 2015 +0200
Commit: Jani Nikula <jani.nikula at intel.com>
CommitDate: Thu Jun 4 11:44:37 2015 +0300
drm/i915: Implement intel_crtc_control using atomic state, v4
Assume the callers lock everything with drm_modeset_lock_all.
This change had to be done after converting suspend/resume to
use atomic_state so the atomic state is preserved, otherwise
all transitional state is erased.
Now all callers of .crtc_enable and .crtc_disable go through
atomic modeset! :-D
Changes since v1:
- Only check for crtc_state->active in valleyview_modeset_global_pipes.
- Only check for crtc_state->active in modeset_update_crtc_power_domains.
Changes since v2:
- Rework on top of the changed patch order.
Changes since v3:
- Rename intel_crtc_toggle in description to *_control
- Change return value to int.
- Do not add plane state, should be done implicitly already.
Signed-off-by: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
Reviewed-by: Matt Roper <matthew.d.roper at intel.com>
Signed-off-by: Jani Nikula <jani.nikula at intel.com>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150617/b48bc09a/attachment.html>
More information about the intel-gfx-bugs
mailing list