[Bug 73688] New: [Regression HSW ULT] Calltrace when system resume from S4: WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/i915/intel_display.c:10299 intel_get_pipe_from_connector+0x26/0x3c [i915]()

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 73688
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: jbarnes at virtuousgeek.org
           Summary: [Regression HSW ULT] Calltrace when system resume from
                    S4: WARNING: CPU: 0 PID: 6 at
                    drivers/gpu/drm/i915/intel_display.c:10299
                    intel_get_pipe_from_connector+0x26/0x3c [i915]()
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: qingshuai.tian at intel.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Created attachment 92209
  --> https://bugs.freedesktop.org/attachment.cgi?id=92209&action=edit
dmesg after system resume from s4

Environment:
-------------------
  Kernel: (drm-intel-next-queued) f1fcde49872f390a4060fa9ee8b02d3f2a8508b7
  Machin Info: Lenovo idealpad u330p

Description:
--------------------
When testing s4 on a HSW ULT, there is Call trace information in dmesg after
the machine resume. You can check the dmesg in the attachment. 
The Call trace will disappear when test with parameter "i915.modeset=0".
It's a regression, and I biscted it.

Bisect shows:
--------------------
752aa88a1e784c22d514db3b440e49427b58259e is the first bad commit
commit 752aa88a1e784c22d514db3b440e49427b58259e
Author: Jesse Barnes <jbarnes at virtuousgeek.org>
Date:   Thu Oct 31 18:55:49 2013 +0200

    drm/i915: make backlight functions take a connector

    On VLV/BYT, backlight controls a per-pipe, so when adjusting the
    backlight we need to pass the correct info.  So make the externally
    visible backlight functions take a connector argument, which can be used
    internally to figure out the pipe backlight to adjust.

    v2: make connector pipe lookup check for NULL crtc (Jani)
        fixup connector check in ASLE code (Jani)
    v3: make sure we take the mode config lock around lookups (Daniel)
    v4: fix double unlock in panel_get_brightness (Daniel)
    v5: push ASLE work into a work queue (Daniel)
    v6: separate ASLE work to a prep patch, rebase (Jani)

    Signed-off-by: Jesse Barnes <jbarnes at virtuousgeek.org>
    Signed-off-by: Jani Nikula <jani.nikula at intel.com>
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>

:040000 040000 8c3767165764c6e36b90d9e62b1e23940071d909
2d0aa55819f045debb6e14208bc30e6de516255f M   drivers


Test Step:
--------------------
1.boot up machine
2.echo disk > /sys/power/state

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140116/a67f0f9a/attachment.html>