[Bug 63453] New: [ILK] testdisplay cause Call Trace with DP pipe

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 63453
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [ILK] testdisplay cause Call Trace with DP pipe
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: major
    Classification: Unclassified
                OS: All
          Reporter: yangweix.shui at intel.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Created attachment 77844
  --> https://bugs.freedesktop.org/attachment.cgi?id=77844&action=edit
dmesg of running display with DP cause call trace

Environment:
--------------------------
commit e8aeaee7b012f1cdb382765d17307445385aa87c
Author: Daniel Vetter <daniel.vetter at ffwll.ch>
Date:   Sat Jul 21 16:47:09 2012 +0200

    drm/i915: unbreak lastclose for failed driver init

    We now refuse to load on gen6+ if kms is not enabled:

    commit 26394d9251879231b85e6c8cf899fa43e75c68f1
    Author: Daniel Vetter <daniel.vetter at ffwll.ch>
    Date:   Mon Mar 26 21:33:18 2012 +0200

        drm/i915: refuse to load on gen6+ without kms

    Which results in the drm core calling our lastclose function to clean
    up the mess, but that one is neatly broken for such failure cases
    since kms has been introduced in

    commit 79e539453b34e35f39299a899d263b0a1f1670bd
    Author: Jesse Barnes <jbarnes at virtuousgeek.org>
    Date:   Fri Nov 7 14:24:08 2008 -0800

        DRM: i915: add mode setting support

    Reported-and-tested-by: Paulo Zanoni <przanoni at gmail.com>
    Signed-Off-by: Daniel Vetter <daniel.vetter at ffwll.ch>

Description:
---------------------
When I testdisplay with DP plugged on ILK platform, it will come up a "Call
Trace". Because we usually test our testing on another ILK machine, so this bug
we haven't found immediately. This bug is caused between "Linux 3.6" and "Linux
3.7". I tried to bisect, but there's too many merge commit in it. I can't find
the first bad, when I bisect commit to
e8aeaee7b012f1cdb382765d17307445385aa87c, there's information on terminal like
below:
##########################
[root at x-kernel drm-intel]# git bisect bad
e8aeaee7b012f1cdb382765d17307445385aa87c
The merge base a0d271cbfed1dd50278c6b06bead3d00ba0a88f9 is bad.
This means the bug has been fixed between
a0d271cbfed1dd50278c6b06bead3d00ba0a88f9 and
[65b99c74fdd325d1ffa2e5663295888704712604 
6d55d5968a8622f3ea20ec40737aea1cfba6438c
979570e02981d4a8fc20b3cc8fd651856c98ee9d
a0d271cbfed1dd50278c6b06bead3d00ba0a88f9
aecdc33e111b2c447b622e287c6003726daa1426].

statement:
------------------
I have appended the dmesg in attachment. If you need more information or
something else needed, please comment, I'm glad to working for this.

-- 
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/20130412/ae9a6703/attachment.html>