Bug 20723 - [915gm KMS UMS]S3 can not resume
Summary: [915gm KMS UMS]S3 can not resume
Status: CLOSED NOTOURBUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: ykzhao
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-17 22:26 UTC by liuhaien
Modified: 2017-10-06 14:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg.0.log (30.06 KB, text/plain)
2009-03-17 22:26 UTC, liuhaien
no flags Details
reg_dumper_pre_s3 (8.71 KB, text/plain)
2009-03-17 22:29 UTC, liuhaien
no flags Details

Description liuhaien 2009-03-17 22:26:57 UTC
Created attachment 23986 [details]
xorg.0.log

System Environment:
--------------------------
Host:          915gm
Arch:           i386
Libdrm:         (master)2e2e8575b1ed4703653a72ac2b60b75316c388d7
Mesa:      (mesa_7_4_branch)a8528a2e8653b5237c1d1d66fe98c6e031d007f9
Xserver:(server-1.6-branch) 60c161545af80eb78eb790a05bde79409dfdf16e
Xf86_video_intel:                (2.7)238c2c40afd9f8b61479b8640d53f20d52fd7ddf
Kernel:       (for-airlied)dc529a4fe1ae4667c819437a94185e8581e1e680

Bug detailed description:
--------------------------
start X with KMS enabled, we test S3 on 915gm. the machine can suspend but resume,
after suspending, the system seems locked, the only thing we can do is that force off and reboot by pushing the power button.

Reproduce steps:
----------------------------
1.xinit&
2. echo mem >/sys/power/state
Comment 1 liuhaien 2009-03-17 22:29:26 UTC
Created attachment 23987 [details]
reg_dumper_pre_s3
Comment 2 liuhaien 2009-03-18 01:52:58 UTC
let me make it clear, after suspending , I try to push the power button to resume this machine, but there is no response. we can only push the button for some seconds to power off then restart .
Comment 3 liuhaien 2009-03-18 01:53:18 UTC
and s3 works with UMS.
Comment 4 ykzhao 2009-03-29 22:34:19 UTC
Hi, Haien
    Will you please confirm whether this is a blank issue or the box can't be resumed at all?
    Will you please boot the box with KMS and do the following test?
    a. add the boot option of "acpi_sleep=beep"
    b. kill the process that is using the /proc/acpi/event(use the command of "lsof /proc/acpi/event" to get the process)
    c. echo mem > /sys/power/state; dmesg >dmesg_after;
    d. press the power button and see whether the beep voice can be heard.

    If there is no beep voice, please reboot the box and see whether there exists the file of dmesg_after.

    If there exists the file of dmesg_after, maybe this is a blank issue. 
    Thanks.
Comment 5 liuhaien 2009-03-30 22:36:58 UTC
(In reply to comment #4)
> Hi, Haien
>     Will you please confirm whether this is a blank issue or the box can't be
> resumed at all?
>     Will you please boot the box with KMS and do the following test?
>     a. add the boot option of "acpi_sleep=beep"
>     b. kill the process that is using the /proc/acpi/event(use the command of
> "lsof /proc/acpi/event" to get the process)
>     c. echo mem > /sys/power/state; dmesg >dmesg_after;
>     d. press the power button and see whether the beep voice can be heard.
> 
>     If there is no beep voice, please reboot the box and see whether there
> exists the file of dmesg_after.
> 
>     If there exists the file of dmesg_after, maybe this is a blank issue. 
>     Thanks.
> 

hi,yakui
  I have tried it follow you say.there is no beep voice.and the sleep indicator  light stays green when I push the power button first. I can not access it by remote(ssh).the only thing I can do is just poweroff it by pushing the button forcibly for some seconds and restart. but what make me confused is there exists the file of dmesg_after,maybe you should come and check it.
Comment 6 liuhaien 2009-04-08 02:09:28 UTC
this issue also happens with UMS(both uxa and exa).
Comment 7 liuhaien 2009-04-08 02:16:03 UTC
(In reply to comment #6)
> this issue also happens with UMS(both uxa and exa).
> 

and it often happens on the second suspend-resume. 
Comment 8 ykzhao 2009-06-08 20:16:09 UTC
Hi, Haien
    Do you have an opportunity to try the latest kernel(2.6.30-rc7) and see whether the box still can't be resumed?
    A bunch of acpi patches are shipped between 2.6.29 and 2.6.30-rc7.
   Thanks.
Comment 9 Michael Fu 2009-08-04 22:15:24 UTC
found this for Thinkpad R52 on http://mathema.tician.de/hardware/r52 :

"Suspend to Disk is straightforward, for Suspend to RAM to work you need one little non-obvious trick: specify acpi_sleep=s3_bios on the command line"
Comment 10 fangxun 2009-08-06 21:53:23 UTC
Verified with adding "acpi_sleep=s3_bios" on kernel boot option.
Comment 11 Elizabeth 2017-10-06 14:55:02 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.