Bug 67337 - [SNB IVB HSW]S4 fails to resume sporadically
Summary: [SNB IVB HSW]S4 fails to resume sporadically
Status: CLOSED NOTOURBUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium major
Assignee: shui yangwei
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-26 07:55 UTC by cancan,feng
Modified: 2017-10-06 14:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
S4 dmesg on HSW (173.06 KB, text/plain)
2013-07-26 07:55 UTC, cancan,feng
no flags Details
without i915: screen output (1.20 MB, image/jpeg)
2013-08-09 07:48 UTC, shui yangwei
no flags Details

Description cancan,feng 2013-07-26 07:55:48 UTC
Created attachment 83016 [details]
S4 dmesg on HSW

Environment:
-------------------
Kernel: (drm-intel-next-queued)3b27af3560f3cfe4e09171024515fa304ebae93b
Author: Imre Deak <imre.deak@intel.com>
Date:   Thu Jul 25 16:22:31 2013 +0300

    drm/i915: dvo_ch7xxx: fix vsync polarity setting

Description:
--------------------
S4 fails to resume less then 20 times while doing S4 cycles on -next-queued branch. This issue happens on SNB,IVB and HSW platforms. Here I attach a dmesg which I got from S4 cycle on HSW desktop using serial port. In this cycle, S4 fails to resume at the 2nd time. The screen is black, and it's just stuck in there. 

Reproduce step:
----------------------
1.xinit&
2.gnome-session&
2.do S4 cycle
Comment 1 Jani Nikula 2013-08-08 14:07:18 UTC
Please try this without i915 loaded so we can see if this is related to our driver in the first place.

If that works, please try with i915 again, using drm.debug=0xe module parameter.
Comment 2 shui yangwei 2013-08-09 07:48:04 UTC
Created attachment 83876 [details]
without i915: screen output

(In reply to comment #1)
> Please try this without i915 loaded so we can see if this is related to our
> driver in the first place.
> 
> If that works, please try with i915 again, using drm.debug=0xe module
> parameter.

(In reply to comment #1)
> Please try this without i915 loaded so we can see if this is related to our
> driver in the first place.
> 
> If that works, please try with i915 again, using drm.debug=0xe module
> parameter.

S4 also failed to resume after removing i915, I noticed that the screen is not black, and the machine is reachable. I said it failed, because my script stopped, and the screen output is strange. I loop running S4 test for two times, the first time it failed at 9th round, the second time it failed at 6th round. 

There's quite a little things in dmesg, I pasted it here:
---------------------------------
[83963.438834] cl-api-create-p[6317]: segfault at 0 ip 0000003cd355f791 sp 00007ffff7d5ccf8 error 4 in libc-2.15.so[3cd3400000+1ac000]
[2642043.120562] e1000e: eth1 NIC Link is Down
[2642044.724906] e1000e: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[2642044.724909] e1000e 0000:02:00.0: eth1: 10/100 speed: disabling TSO
[5931798.505398] libcl.so[32650]: segfault at 18bf4 ip 00000000f7797bfb sp 00000000ffa05414 error 6 in libcl.so[f7787000+18000]
Comment 3 Jani Nikula 2013-08-09 07:57:39 UTC
Like in bug 66951: reproducible without our driver -> NOTOURBUG.
Comment 4 Elizabeth 2017-10-06 14:44:46 UTC
Closing old verified.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.