What happens if you use DP or eDP instead of HDMI?

Created attachment 88096 [details]
dmesg of s3 fail (DP)

When I test s3 on the machine with DP instead of HDMI, the Call trace disappeared. But the s3 still didn't work.

(In reply to comment #2)
> Created attachment 88096 [details]
> dmesg of s3 fail (DP)
> 
> When I test s3 on the machine with DP instead of HDMI, the Call trace
> disappeared. But the s3 still didn't work.

Can you please try to bisect this problem?

Thanks,
Paulo

I have finished the bisect, and the result shows:

24576d23976746cb52e7700c4cadbf4bc1bc3472 is the first bad commit
commit 24576d23976746cb52e7700c4cadbf4bc1bc3472
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Tue Mar 26 09:25:45 2013 -0700

    drm/i915: enable VT switchless resume v3

    With the other bits in place, we can do this safely.

    v2: disable backlight on suspend to prevent premature enablement on resume
    v3: disable CRTCs on suspend to allow RTD3 (Kristen)

    Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
    Reviewed-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

I hope it's helpful.  :)

Yup, bisect is helpful. This sounds like a dupe of bug #64379

But I dunno really why DP fails silently, so maybe it's better to track this separately.

Which BIOS version are you using on this machine? Can you please update to the latest?

(In reply to comment #4)
> I have finished the bisect, and the result shows:
> 
> 24576d23976746cb52e7700c4cadbf4bc1bc3472 is the first bad commit
> commit 24576d23976746cb52e7700c4cadbf4bc1bc3472
> Author: Jesse Barnes <jbarnes@virtuousgeek.org>
> Date:   Tue Mar 26 09:25:45 2013 -0700
> 
>     drm/i915: enable VT switchless resume v3
> 
>     With the other bits in place, we can do this safely.
> 
>     v2: disable backlight on suspend to prevent premature enablement on
> resume
>     v3: disable CRTCs on suspend to allow RTD3 (Kristen)
> 
>     Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
>     Reviewed-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
>     Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> I hope it's helpful.  :)

Just to be clear: even if you use DP instead of HDMI, then S3 won't work, the only difference is that you won't be seeing that calltrace in dmesg. Is this correct?

What I asked you to bisect was the "S3 doesn't work with DP" problem of this bug, since that really should be a recent regression in case it's happening at all.

Yes. The only difference when I use DP instead of HDMI is that I won't see the call trace. But S3 won't work no matter with HDMI or DP.

What I bisected in comment 4 is for the problem "S3 call trace with HDMI". Sorry that I didn't make it clear.

I tried to bisect the "S3 doesn't work with DP" problem of this bug, but I can't find a goog commit on the drm-intel-next-queued branch.
Even when I tested with the "i915.modeset=0" module, S3 still won't work.

I update the BIOS version from "HSWLPTU1.86C.0120.R00.1303312001" to "HSWPTU1.86C.0134.R00.1310022130". But this problem still exits.

(In reply to comment #8)
> Yes. The only difference when I use DP instead of HDMI is that I won't see
> the call trace. But S3 won't work no matter with HDMI or DP.
> 
> What I bisected in comment 4 is for the problem "S3 call trace with HDMI".
> Sorry that I didn't make it clear.
> 
> I tried to bisect the "S3 doesn't work with DP" problem of this bug, but I
> can't find a goog commit on the drm-intel-next-queued branch.
> Even when I tested with the "i915.modeset=0" module, S3 still won't work.
> 
> I update the BIOS version from "HSWLPTU1.86C.0120.R00.1303312001" to
> "HSWPTU1.86C.0134.R00.1310022130". But this problem still exits.

Can you please try to completely blacklist i915.ko and see if the problem still happens? In this case, it's not our bug.

Yes.After I disabled  the i915.ko, the s3 problem still happen.

We still need to identify which component is failing so that we can file an appropriate bug report.

Closing old verified.