Suspend to Ram/Disk on Samsung X30 WV1500 does not work

[Caspar Clemens Mierau]

Binary package hint: acpi-support

As you requested bug reports for this on Linuxtag here you are:

Suspend to Ram/Disk does not work on a Samsung X30 WV1500 on Ubuntu Feisty.

The Laptop suspends but has problems recovering.

Suspend to Ram: It seems to suspend, you can afterwards wake him up, see some lines of text for one or two seconds, then the screen gets blank and the machine stays in this state. I tried to switch through the consoles with no success.

Suspend to Disk: The laptop suspends, but on a new boot the laptop just boots into normal state and ignores the last suspend.

My laptop has three customizations though I don't think they are involved in this:

1. I exchanged the hard disk (bigger one=
2. I extended the Ram
3. I exchanged the wlan adapter to a Centrino (wlan g) ipw2200 one (works great)

I also added some luks crypto stuff with the standard Ubuntu tools but the suspend stuff did not work before either.

[sam tygier (samtygier)]

please can you follow the instructions at
https://wiki.ubuntu.com/DebuggingKernelSuspend
to gather some useful information.

also please attach the output of lspci -vv and lspci -vvn

[Caspar Clemens Mierau (leitmedium)]

I followed the Debug procedure and attach hereby the dmesg output. I had, of course, to reboot the machine after trying to resume as I got the blank screen again. For your information: The hard drive light flashes a bit after resume.

Let me know if I can provide you with any further details.

[Caspar Clemens Mierau (leitmedium)]

Hi,

for further debugging I started the kerneldebugging procedure from command line (without gnome).

I got some more error messages that might be interesting:

From Suspend:

ipw2200: Failed to send CARD_DISABLE: command timed out
Shutting down Alsa
Function not supported
Function not supported

From Resume:

skipping unknown interface eth0=eth0

[Caspar Clemens Mierau (leitmedium)]

I checked removen the ipw2200 driver before suspend with no impact on resuming. It behaves the same way, so ipw2200 is not the problem.

[Caspar Clemens Mierau (leitmedium)]

I tested Suspend To Ram / Hibernate with Gutsy Tribe-2 Live CD without success. The laptop goes to sleep, seems to wake up on pressing the power button but the screen stays blank.

[Caspar Clemens Mierau (leitmedium)]

Thanks for the adding of "affects to". Is there anything more I can provide you with? Think I'll have the time in a couple of days to check against the most recent Gutsy Tribe though a first check already has been negative on that point.

[Henrik Nilsen Omma (henrik)]

Thanks for providing the debugging output. Setting to confirmed.

[Brian Murray (brian-murray)]

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

[Tobias Wolf (towolf)]

BTW, I had resume from suspend on my Samsung X30 1700 working for a long time (since Feisty), but it stopped working after clean-installing Gutsy.
I had problems to reconstruct my settings, even now on Hardy with new pm-utils I found that I still get funny colors after resume, but when I switch the screen off and on again with sudo vbetool dpms off; sudo vbetool dpms on, the desktop comes back. No other quirks settings are necessary, but I would love to know how why the DPMS off/on does the trick. The dpms quirks do something else I assume, because the screen switches off, is suspended, switches on, and then the funny matrix-like stripes appear.

Could we include this quirk for Hardy in this bug report but with the notice that the solution seems really close?

[borsdel (borsdel)]

The solution posted above by Tobias Wolf does work! Thanks
Now I need to find a way do this automatically on resume.
mfg borsdel
ps on gentoo I have the same issue ;)

[Tobias Wolf (towolf)]

This is my suspend script

$ cat /usr/local/bin/suspend
#!/bin/sh
pm-suspend
vbetool dpms off
vbetool dpms on

I call "sudo suspend" and it works reliably.

[borsdel (borsdel)]

On gentoo I use hibernate-script and got it working with this config from /etc/hibernate/common.conf

### vbetool
EnableVbetool yes
RestoreVbeStateFrom /var/lib/vbetool/vbestate
# VbetoolPost yes
# RestoreVCSAData yes

I think to restore the vbestate isn't necessary (as on ubuntu) but VbetoolRestoreState() from /usr/share/hibernate/scriptlets.d/vbetool will do the "quirk" with the dpms stuff.

@Tobias: Thank you for your suspend script, I will try it out on Ubuntu.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Tobias Wolf (towolf)]

I run 2.6.27-2-generic now and the screen still does not recover after resume.
When I resume, the screen in initially black, but backlit. Then gradually colored corruptions appear until the screen is full of eerie looking corruptions. The desktop is fine, because I can blindly type, etc.

Now, to recover the screen, I still have to power-cycle the LCD with the above method (DPMS off, DPMS on).

So, no change with 2.6.27.

[Leann Ogasawara (leannogasawara)]

Hi Tobias,

Can you attach your dmesg output after an attempted Suspend/Resume cycle?

[Tobias Wolf (towolf)]

Here you go. Is there anything going wrong you can discern in the log?
[voff and von are aliases for commands I mentioned above]

towolf@sams:~$ sudo dmesg -c > /dev/null
towolf@sams:~$ sudo pm-suspend
towolf@sams:~$ ...blindly...
bash: ...blindly...: command not found
towolf@sams:~$ voff
towolf@sams:~$ von
towolf@sams:~$ dmesg
[ 567.756068] PM: Syncing filesystems ... done.
[ 567.769726] PM: Preparing system for mem sleep
[ 567.770724] Freezing user space processes ... (elapsed 0.00 seconds) done.
[ 567.773577] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[ 567.773789] PM: Entering mem sleep
[ 567.773796] Suspending console(s) (use no_console_suspend to debug)
[ 567.792059] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 567.792238] sd 0:0:0:0: [sda] Stopping disk
[ 569.381250] eth1: Going into suspend...
[ 569.382128] ipw2200 0000:02:07.0: PCI INT A disabled
[ 569.396071] b44 0000:02:05.0: PCI INT A disabled
[ 569.432144] NVRM: RmPowerManagement: 4
[ 570.379267] Intel ICH 0000:00:1f.5: PCI INT B disabled
[ 570.379520] ata_piix 0000:00:1f.1: PCI INT A disabled
[ 570.379612] ehci_hcd 0000:00:1d.7: PCI INT D disabled
[ 570.392075] uhci_hcd 0000:00:1d.2: PCI INT C disabled
[ 570.392103] uhci_hcd 0000:00:1d.1: PCI INT B disabled
[ 570.392131] uhci_hcd 0000:00:1d.0: PCI INT A disabled
[ 570.392295] PM: suspend devices took 2.620 seconds
[ 570.392389] ACPI: Preparing to enter system sleep state S3
[ 570.392464] Disabling non-boot CPUs ...
[ 570.392464] Back to C!
[ 570.392464] ACPI: Waking up from system sleep state S3
[ 571.032365] ACPI: EC: non-query interrupt received, switching to interrupt mode
[ 571.040806] ACPI: Transitioning device [FAN0] to D3
[ 571.040836] pci 0000:00:01.0: restoring config space at offset 0xf (was 0x0, writing 0xc0000)
[ 571.040843] pci 0000:00:01.0: restoring config space at offset 0x9 (was 0xfff0, writing 0xdff0d800)
[ 571.040847] pci 0000:00:01.0: restoring config space at offset 0x8 (was 0xfff0, writing 0xcff0c800)
[ 571.040851] pci 0000:00:01.0: restoring config space at offset 0x7 (was 0x2a000f0, writing 0x22a000f0)
[ 571.040855] pci 0000:00:01.0: restoring config space at offset 0x6 (was 0x0, writing 0x40010100)
[ 571.040860] pci 0000:00:01.0: restoring config space at offset 0x3 (was 0x10000, writing 0x16000)
[ 571.040864] pci 0000:00:01.0: restoring config space at offset 0x1 (was 0xa00000, writing 0xa00107)
[ 571.040880] uhci_hcd 0000:00:1d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
[ 571.040885] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 571.040924] usb usb2: root hub lost power or was reset
[ 571.040997] uhci_hcd 0000:00:1d.1: PCI INT B -> Link[LNKD] -> GSI 10 (level, low) -> IRQ 10
[ 571.041002] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 571.041039] usb usb3: root hub lost power or was reset
[ 571.041065] uhci_hcd 0000:00:1d.2: PCI INT C -> Link[LNKC] -> GSI 10 (level, low) -> IRQ 10
[ 571.041070] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 571.041107] usb usb4: root hub lost power or was reset
[ 571.056039] ehci_hcd 0000:00:1d.7: PCI INT D -> Link[LNKH] -> GSI 5 (level, low) -> IRQ 5
[ 571.056044] ...

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Leann Ogasawara (leannogasawara)]

Is this still an issue with Intrepid's final release? If so, it would be great if you'd be willing to give the latest pre-release of Jaunty a try - http://cdimage.ubuntu.com/releases/jaunty/ . You should be able to test suspend via a LiveCD. Also, Jaunty Alpha3 is set to come out in the next day or two so you may want to wait to test. Thanks.

[Tobias Wolf (towolf)]

Still present in Intrepid final. And chance has it that I upgraded to Jaunty yesterday. The screen still doesn’t come up after resume, but I can reanimate using dpms off and on.

Summary, no change at all.

The thing is that it used to work in Feisty without tricks. Not anymore.

[Tobias Wolf (towolf)]

Salve again,

for completeness sake, and to eliminate the possibility that my hd install is somehow pathological, I made myself a Live USB install of the Jaunty Alpha 3.

It was difficult to obtain results, because the problems were even worse than for my normal install. That is, I couldn’t manage to reset the screen with my usual trick.

First, I used the nv driver. But this is difficult because nv renders the desktop corruptly with every other pixel shifted in the pixel grid. Still I managed to suspend and resume, with the same results: The screen comes up darkly, but with eerie color patterns emerging slowly. No effect of vbetool dpms off.

Then, I got the Nvidia legacy driver 173.14.15 beta installed it with the install script and started Xorg with -ignoreABI. The result was similar. After resuming, I could see some colored shades, i.e. the backlight is on, but the screen is corrupted with some colors.

Attached are G-P-M logs for both gfx drivers, and the kern.log containing both boots (I had to reset with SysRq, of course)

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]