Bug 20596 - [KMS GM45] S3/S4 resume gets blank screen for X
Summary: [KMS GM45] S3/S4 resume gets blank screen for X
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium major
Assignee: Jesse Barnes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-11 02:06 UTC by liuhaien
Modified: 2017-10-06 14:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg.0.log (181.90 KB, text/plain)
2009-03-11 02:06 UTC, liuhaien
no flags Details
xorg conf file (3.76 KB, text/plain)
2009-03-11 02:07 UTC, liuhaien
no flags Details
xorg.0.log after suspend (21.33 KB, text/plain)
2009-03-12 18:59 UTC, liuhaien
no flags Details
dmesg after suspend (46.29 KB, text/plain)
2009-03-12 19:00 UTC, liuhaien
no flags Details

Description liuhaien 2009-03-11 02:06:54 UTC
Created attachment 23753 [details]
xorg.0.log

System Environment:
--------------------------
Libdrm:         (master)82eac8060b98b425f29051bfd7830ba3622be7d8
Mesa:           (mesa_7_4_branch)2adaec12267767747a22646c759b0d6c1651d3bf       
Xserver:        (server-1.6-branch)f469726fec502ce29999eda6919c3c3d26c127d8
Xf86_video_intel:               (2.7)4e334ef33c38e2e930958a4b68d79f1860bb9efa
Kernel:       (for-airlied)edde72a59461d766997b469f6d20afdf5fe9b5b4


Bug detailed description:
-------------------------
we tried S3/S4 with KMS enabled, but it can not bring back to X after suspending.we can only get a blank screen, and can access the machine by remote.
the  issue happens on gm45 and acer aspire one.

reproduce steps:
------------------------
1.xinit&
2.echo mem(or disk) >/sys/power/state
3. power on
Comment 1 liuhaien 2009-03-11 02:07:21 UTC
Created attachment 23754 [details]
xorg conf file
Comment 2 Shuang He 2009-03-11 04:11:30 UTC
Acer aspire one has diferent symptom. a separate bug will be filed to track it.
Comment 3 Shuang He 2009-03-11 19:12:53 UTC
(In reply to comment #2)
> Acer aspire one has diferent symptom. a separate bug will be filed to track it.
> 

tracked with bug #20613
Comment 4 Jesse Barnes 2009-03-12 16:33:15 UTC
I just tried with master of everything today (using drm-intel-next) and my GM45 system is resuming well, even w/compiz running.  Can you give that a try?

The log you posted doesn't contain a VT switch either, which means it must be from before the suspend?
Comment 5 liuhaien 2009-03-12 18:59:19 UTC
Created attachment 23818 [details]
xorg.0.log after suspend
Comment 6 liuhaien 2009-03-12 19:00:14 UTC
Created attachment 23819 [details]
dmesg after suspend
Comment 7 liuhaien 2009-03-12 19:08:34 UTC
(In reply to comment #4)
> I just tried with master of everything today (using drm-intel-next) and my GM45
> system is resuming well, even w/compiz running.  Can you give that a try?
> 
> The log you posted doesn't contain a VT switch either, which means it must be
> from before the suspend?
> 

still broke on my side(using for-airlied).the dmesg and the xorg.0.log after suspend are attached.
Comment 8 Jesse Barnes 2009-04-10 16:13:03 UTC
Works for me with latest libdrm, xf86-video-intel and drm-intel-next.
Comment 9 liuhaien 2009-04-13 20:24:03 UTC
(In reply to comment #8)
> Works for me with latest libdrm, xf86-video-intel and drm-intel-next.
> 

it works with drm-intel-next, but still broken with drm-intel-2.6.29.
Comment 10 Jesse Barnes 2009-05-04 11:09:49 UTC
Ok, marking as fixed, but it would be good if you could find which patch fixed it.
Comment 11 liuhaien 2009-05-14 20:44:04 UTC
verified against:
Libdrm:		(master)8b8e20e0f9900fae23baee55a91533a739c1a3ec
Mesa:		(master)d3912e301fd707738b0952cd11e19f34b87765b8
Xserver:		(master)2075d4bf9e53b8baef0b919da6c44771220cd4a5
Xf86_video_intel:		(master)1c68bc376a9cb3c0a010c8e28f69a776755c8f64
Kernel:       (for-linus)79f11c19a396e8cea7dad322dcfb46c0a8517fe6
Comment 12 Elizabeth 2017-10-06 14:55:19 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.