[Bug 82281] [PNV/HSW/BSW Bisected]igt/kms_universal_plane/universal-plane-pipe-A-functional tests timeout
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Nov 25 01:19:20 PST 2014
https://bugs.freedesktop.org/show_bug.cgi?id=82281
Guo Jinxian <jinxianx.guo at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
--- Comment #6 from Guo Jinxian <jinxianx.guo at intel.com> ---
(In reply to Matt Roper from comment #5)
> (In reply to Daniel Vetter from comment #4)
> > Guo, can you please retest? We've merged a few patches meanwhile.
> >
> > Matt, can you please point Guo at a branch with your latest pile of
> > universal plane fixes if -nightly is still broken?
>
> Yeah, I don't see any obvious red flags in the dmesg (aside from 5 seconds
> between starting and stopping CRC collection), so I'm not sure if this will
> be helped by any of the patches I've recently written or not.
>
> If it does still occur with latest di-nightly, you can also try using branch
> "forupstream/display-refactor-v3" from the repo at
> https://github.com/mattrope/kernel.git , although I'm not sure whether
> anything in there will help or not.
Test still timeout on this tree
[root at x-pnv2 tests]# ./kms_universal_plane --run-subtest
universal-plane-pipe-A-functional
IGT-Version: 1.8-gd807891 (i686) (Linux: 3.18.0-rc6_glody_7d9306_20141125+
i686)
Testing connector LVDS-1 using pipe A
Subtest universal-plane-pipe-A-functional: TIMEOUT (5.084s)
commit:
commit 7d93064ed0238483385721930df71c3561f43fd5
Author: Matt Roper <matthew.d.roper at intel.com>
Date: Fri Nov 21 15:52:28 2014 -0800
drm/i915: Make all plane disables use 'update_plane'
If we extend the commit_plane handlers for each plane type to be able to
handle fb=0, then we can easily implement plane disable via the
update_plane handler. The cursor plane already works this way, and this
is the direction we need to go to integrate with the atomic plane
handler. We can now kill off the type-specific disable functions, as
well as the redundant intel_plane_disable() (not to be confused with
intel_disable_plane()).
Note that prepare_plane_fb() only gets called as part of update_plane
when fb!=NULL (by design, to match the semantics of the atomic plane
helpers); this means that our commit_plane handlers need to handle the
frontbuffer tracking for the disable case, even though they don't handle
it for normal updates.
Signed-off-by: Matt Roper <matthew.d.roper 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20141125/69c88fd3/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list