[Bug 79311] Call trace originating from i915 referencing intel_wait_for_vblank()

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Fri Sep 5 07:18:22 PDT 2014


https://bugzilla.kernel.org/show_bug.cgi?id=79311

--- Comment #21 from Alan Bartlett <ajb at elrepo.org> ---
(In reply to Jani Nikula from comment #20)
> The regressing commit is
> 
> commit 56ef52cad5e37fca89638e4bad598a994ecc3d9f
> Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
> Date:   Thu May 8 19:23:15 2014 +0300
> 
>     drm/i915: Kill vblank waits after pipe enable on gmch platforms
>     
>     The pipe might not start to actually run until the port has been enabled
>     (depends on the platform and port type). So don't try to wait for vblank
>     after we enabled the pipe but haven't yet enabled the port.
>     
>     Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
>     Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk>
>     References: https://bugs.freedesktop.org/show_bug.cgi?id=77297
>     Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>

The defect was first noticed and reported on July 1st 2014. The current date is
now September 5th 2014.

Has there been any action? Is there anything ready for me to test? A simple
patch would be to revert the above commit. Unfortunately as other commits have
now overlaid the regressing commit, it is not something I can do.

Maintainers -- Your comments, please.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the intel-gfx-bugs mailing list