Comment 53 for bug 1566828

Revision history for this message
Jonas Schwabe (jonas-schwabe) wrote :

Finished my bisect:

7bb4014e065abf88c1698bc5fde7a91caf907265 is the first bad commit
commit 7bb4014e065abf88c1698bc5fde7a91caf907265
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>
    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

Which matches this commit in the upstream git: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f95429eccc570dc45d589c327bfcfddcdc3e8228

Turns out I have not been the first one, doing this: https://bugzilla.kernel.org/show_bug.cgi?id=112781

...
Which has been fixed here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e5f243bd2edd95c6cc1d90c1878f821068e83fba.

I picket the patch and check if the problem is gone.