7bb4014e065abf88c1698bc5fde7a91caf907265 is the first bad commit
commit 7bb4014e065abf88c1698bc5fde7a91caf907265
Author: Rob Clark <email address hidden>
Date: Mon Jan 25 18:06:48 2016 -0500
This fixes an issue that was noticed on an optimus/prime laptop with
a kernel that was old enough to not support the integrated intel gfx
(which was driving all the outputs), but did have support for the
discrete radeon gpu. The end result was not falling back to VESA and
leaving the user with a black screen.
(Plus it is kind of silly to create an framebuffer device if there
are no outputs hooked up to the gpu.)
Signed-off-by: Rob Clark <email address hidden>
Signed-off-by: Alex Deucher <email address hidden>
(cherry picked from commit f95429eccc570dc45d589c327bfcfddcdc3e8228)
Signed-off-by: Alberto Milone <email address hidden>
Signed-off-by: Tim Gardner <email address hidden>
:040000 040000 e8135e481d51ce133b7c3e5ee97f0916fb731bb5 230277112d1123be03dbec1be4f597057e91e546 M drivers
Finished my bisect:
7bb4014e065abf8 8c1698bc5fde7a9 1caf907265 is the first bad commit 8c1698bc5fde7a9 1caf907265
commit 7bb4014e065abf8
Author: Rob Clark <email address hidden>
Date: Mon Jan 25 18:06:48 2016 -0500
drm/radeon: only init fbdev if we have connectors
BugLink: http:// bugs.launchpad. net/bugs/ 1546572
This fixes an issue that was noticed on an optimus/prime laptop with
a kernel that was old enough to not support the integrated intel gfx
(which was driving all the outputs), but did have support for the
discrete radeon gpu. The end result was not falling back to VESA and
leaving the user with a black screen.
(Plus it is kind of silly to create an framebuffer device if there
are no outputs hooked up to the gpu.)
Signed-off-by: Rob Clark <email address hidden> 45d589c327bfcfd dcdc3e8228)
Signed-off-by: Alex Deucher <email address hidden>
(cherry picked from commit f95429eccc570dc
Signed-off-by: Alberto Milone <email address hidden>
Signed-off-by: Tim Gardner <email address hidden>
:040000 040000 e8135e481d51ce1 33b7c3e5ee97f09 16fb731bb5 230277112d1123b e03dbec1be4f597 057e91e546 M drivers
Which matches this commit in the upstream git: https:/ /git.kernel. org/cgit/ linux/kernel/ git/torvalds/ linux.git/ commit/ ?id=f95429eccc5 70dc45d589c327b fcfddcdc3e8228
Turns out I have not been the first one, doing this: https:/ /bugzilla. kernel. org/show_ bug.cgi? id=112781
... /git.kernel. org/cgit/ linux/kernel/ git/torvalds/ linux.git/ commit/ ?id=e5f243bd2ed d95c6cc1d90c187 8f821068e83fba.
Which has been fixed here: https:/
I picket the patch and check if the problem is gone.