Bug 90911 - [PNV] S3 /S4 resume cause call trace, and screen failed to light up after resume while X is running.
Summary: [PNV] S3 /S4 resume cause call trace, and screen failed to light up after res...
Status: CLOSED DUPLICATE of bug 90396
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-09 07:25 UTC by Ding Heng
Modified: 2017-07-24 22:46 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (124.82 KB, text/plain)
2015-06-09 07:25 UTC, Ding Heng 		no flags Details
xorg log (17.26 KB, text/plain)
2015-06-09 07:28 UTC, Ding Heng 		no flags Details
dmesg with drm.debug=0x1e (247.48 KB, text/plain)
2015-06-10 01:49 UTC, Ding Heng 		no flags Details
View All

Description Ding Heng 2015-06-09 07:25:14 UTC 
Created attachment 116385 [details]
dmesg

System Environment:
--------------------------
Regression: not sure.
Platform: PNV

kernel: drm-intel-testing-05-22


Bug detailed description:
-----------------------------

S3 and S4 will cause call trace in dmesg. Screen will fail to light up after S3/S4 resume while X is running.


Reproduce steps:
---------------------------

1. xinit &
2. echo mem > /sys/power/state
3. resume and check if the screen shows normally.
4. kill X and check dmesg.
Comment 1 Ding Heng 2015-06-09 07:28:54 UTC 
Created attachment 116386 [details]
xorg log
Comment 2 Ander Conselvan de Oliveira 2015-06-09 08:05:40 UTC 
This might be a duplicate of bug 90396, where the force restore modeset fails in the atomic checks. Could you reproduce the bug again with 'drm.debug=0x1e log_buf_len=4M' in the kernel command line and attach dmesg again?
Comment 3 Ding Heng 2015-06-10 01:49:01 UTC 
Created attachment 116410 [details]
dmesg with drm.debug=0x1e
Comment 4 Ding Heng 2015-06-10 03:04:51 UTC 
(In reply to Ander Conselvan de Oliveira from comment #2)
> This might be a duplicate of bug 90396, where the force restore modeset
> fails in the atomic checks. Could you reproduce the bug again with
> 'drm.debug=0x1e log_buf_len=4M' in the kernel command line and attach dmesg
> again?

I had tried the bisect commit in bug 90396, this kernel works well on PNV.
Comment 5 Ander Conselvan de Oliveira 2015-06-10 06:34:36 UTC 
(In reply to Ander Conselvan de Oliveira from comment #2)
> This might be a duplicate of bug 90396, where the force restore modeset
> fails in the atomic checks. Could you reproduce the bug again with
> 'drm.debug=0x1e log_buf_len=4M' in the kernel command line and attach dmesg
> again?

[  295.839385] [drm:drm_atomic_helper_check_modeset] [CRTC:22] enabled/connectors mismatch

...

[  295.839449] [drm:drm_atomic_helper_check_modeset] [CRTC:19] enabled/connectors mismatch

It's the same bug.

*** This bug has been marked as a duplicate of bug 90396 ***

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.