[Bug 90929] [BDW/BSW/SKL Bisected]system boot fail
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Jun 10 19:49:47 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=90929
lu hua <huax.lu at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jani.nikula at intel.com
Summary|[BSW/BDW/SKL |[BDW/BSW/SKL
|Regression]system boot fail |Bisected]system boot fail
--- Comment #1 from lu hua <huax.lu at intel.com> ---
Bisect shows:f662af8c5c1619b91e3834fff103e7423e20df81 is the first bad commit
commit f662af8c5c1619b91e3834fff103e7423e20df81
Author: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
AuthorDate: Wed Jun 10 10:24:20 2015 +0200
Commit: Jani Nikula <jani.nikula at intel.com>
CommitDate: Wed Jun 10 14:57:40 2015 +0300
Revert "drm/i915: Read hw state into an atomic state struct, v2."
This reverts commit 3bae26eb2991c00670df377cf6c3bc2b0577e82a.
Seems it introduces regressions for 3 different reasons, oh boy..
In bug #90868 as I can see the atomic state will be restored on
resume without the planes being set up properly. Because plane
setup here requires the atomic state, we'll have to settle
for committing atomic planes first.
In bug #90861 the failure appears to affect mostly DP devices,
and happens because reading out the atomic state prevents a modeset
on boot, which would require better hw state readout.
In bug #90874 it's shown that cdclk should be part of the atomic
state, so only performing a single modeset during resume excarbated
the issue.
It's better to fix those issues first, and then commit this patch,
so do that temporarily.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=90868
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=90861
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=90874
Signed-off-by: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
Acked-by: Ander Conselvan de Oliveira <conselvan2 at gmail.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/20150611/fa2a60e6/attachment.html>
More information about the intel-gfx-bugs
mailing list