[Bug 86551] New: Screen freezes on boot at "fb: switching to inteldrmfb from simple"

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Sun Oct 19 15:59:55 PDT 2014


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

            Bug ID: 86551
           Summary: Screen freezes on boot at "fb: switching to inteldrmfb
                    from simple"
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.17, 3.17.1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: mike.auty at gmail.com
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No

I have a Samsung 700T tablet with an "Intel Corporation 3rd Gen Core processor
Graphcis Controller (rev 09)" according to lspci.  Under <= 3.16.3, it boots
from UEFI and displays at 1920x1080 (the native resolution of the display). 
After a short moment of starting and some kernel output, the screen flashes
black and then reshows itself and the main boot (kernel and post-kernel)
continues.

Under >= 3.17, when booting, the screen will freeze at the line "fb: switching
to inteldrmfb from simple" and no black flash or change in the screen will
happen.

Conducting a git bisection revealed the first bad commit to be
6dda730e55f412a6dfb181cae6784822ba463847 (where the message was "[drm]
Replacing VGA console driver").

Both 3.17 and 3.17.1 are affected.  The machine seems unresponsive (and never
starts a system logger, so I can't see any further messages, or why it doesn't
continue on to the main system).  If I disable modesetting by default it boots
fine, but then X won't start.

I'm happy to provide additional information or run tests, but I'm not sure what
else to provide at this point.

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


More information about the intel-gfx-bugs mailing list