[Bug 64880] New: IVB eDP KMS Black Screen (link training)

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=64880

          Priority: medium
            Bug ID: 64880
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: IVB eDP KMS Black Screen (link training)
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: blocker
    Classification: Unclassified
                OS: Linux (All)
          Reporter: cubicool at gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Created attachment 79683
  --> https://bugs.freedesktop.org/attachment.cgi?id=79683&action=edit
dmesg output

CHIP: IvyBridge GPU (8086:0166)
KERNEL: 3.6.9.1 (vanilla)
DISTRO: Ubuntu 12.04

Bug description: As the machine boots, as soon as KMS throbs the card, the
screen goes entirely black (though brightness still functions) and does not
recover. The system is not locked up, and can be SSH'd into, etc.

Discussing this in IRC the phrase "link training" was used, though I do not
exactly know what indicated such a problem or what the phrase means.

Booting with 'nomodeset i915.modeset=0' lets me use the vesa X driver, and I
get functional (though non-native) virtual consoles.

NOTE: I cannot include any of the register dumps, as I get the following error:

ntel_reg_dumpe:3065 conflicting memory types f7800000-f7c00000
uncached-minus<->write-combining
reserve_memtype failed [mem 0xf7800000-0xf7bfffff], track uncached-minus, req
uncached-minus

System environment:
-- chipset: IvyBridge (8086:0166)
-- system architecture: 64bit
-- kernel: 3.6.9.1 (vanilla)
-- Linux distribution: Ubuntu 12.04
-- Machine or mobo model: Panasonic (prototype)
-- Display connector: eDP-1

-- 
You are receiving this mail because:
You are the QA Contact 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/20130522/ef98214d/attachment.html>