[SOLVED] Unable to initiate suspend to ram

Stunts · 2010-03-08 15:54:57

Hi all!
Everything was fine until a few days ago. I could happily suspend and resume my laptop.
Now the laptop won't suspend. If I hit the suspend button, or let gnome-power-manager do it the result is the same: I get a black screen for a couple of seconds, and then it displays the screensaver, just as if I had hit the "lock screen" button.
Here is my /var/log/pm-suspend.log :

Mon Mar  8 15:46:24 WET 2010: Running hooks for suspend.
/usr/lib/pm-utils/sleep.d/00auto-quirk suspend suspend: Adding quirks from HAL: --quirk-vbe-post 
success.
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: Linux MegalaptopII 2.6.32-ARCH #1 SMP PREEMPT Tue Feb 23 19:43:46 CET 2010 x86_64 Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz GenuineIntel GNU/Linux
Module                  Size  Used by
fuse                   58757  2 
ext2                   62873  1 
usbhid                 38311  0 
hid                    75845  1 usbhid
joydev                  9800  0 
snd_hda_codec_si3054     3862  1 
snd_hda_codec_realtek   250431  1 
arc4                    1354  2 
ecb                     1953  2 
snd_seq_dummy           1439  0 
snd_seq_oss            29023  0 
snd_hda_intel          21810  1 
snd_seq_midi_event      5316  1 snd_seq_oss
iwlagn                109438  0 
uvcvideo               59906  0 
coretemp                4677  0 
snd_hda_codec          63659  3 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel
snd_seq                50558  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
iwlcore                95270  1 iwlagn
videodev               35771  1 uvcvideo
snd_seq_device          5181  3 snd_seq_dummy,snd_seq_oss,snd_seq
cpufreq_powersave        966  0 
cpufreq_ondemand        8101  2 
snd_hwdep               6340  1 snd_hda_codec
snd_pcm_oss            39011  0 
v4l1_compat            15674  2 uvcvideo,videodev
video                  17979  0 
v4l2_compat_ioctl32     9937  1 videodev
acpi_cpufreq            6307  0 
output                  1980  1 video
tpm_infineon            8395  0 
snd_mixer_oss          17299  1 snd_pcm_oss
mac80211              166738  2 iwlagn,iwlcore
snd_pcm                70318  4 snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec,snd_pcm_oss
uhci_hcd               21556  0 
nvidia               9515743  41 
tpm                    11197  1 tpm_infineon
freq_table              2331  2 cpufreq_ondemand,acpi_cpufreq
iTCO_wdt                9093  0 
battery                 9388  0 
tg3                   116187  0 
sdhci_pci               5942  0 
cfg80211              122783  3 iwlagn,iwlcore,mac80211
ehci_hcd               35050  0 
snd_timer              18799  2 snd_seq,snd_pcm
tpm_bios                5481  1 tpm
ac                      3027  0 
i2c_i801                8422  0 
sdhci                  16001  1 sdhci_pci
sg                     25275  0 
firewire_ohci          23569  0 
wmi                     4771  0 
i2c_core               18137  3 videodev,nvidia,i2c_i801
compal_laptop           2627  0 
iTCO_vendor_support     1841  1 iTCO_wdt
rfkill                 15228  1 cfg80211
thermal                11834  0 
snd                    57408  14 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_seq_oss,snd_hda_intel,snd_hda_codec,snd_seq,snd_seq_device,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
usbcore               140485  5 usbhid,uvcvideo,uhci_hcd,ehci_hcd
firewire_core          43019  1 firewire_ohci
psmouse                57028  0 
pcspkr                  1795  0 
evdev                   8825  15 
serio_raw               4440  0 
libphy                 15606  1 tg3
mmc_core               51600  1 sdhci
button                  4714  0 
led_class               2577  2 iwlcore,sdhci
intel_agp              26757  0 
crc_itu_t               1273  1 firewire_core
soundcore               6063  1 snd
snd_page_alloc          7033  2 snd_hda_intel,snd_pcm
processor              30278  3 acpi_cpufreq
rtc_cmos                8904  0 
rtc_core               14631  1 rtc_cmos
rtc_lib                 1810  1 rtc_core
ext4                  334928  2 
mbcache                 5466  2 ext2,ext4
jbd2                   80162  1 ext4
crc16                   1273  1 ext4
sr_mod                 15043  0 
cdrom                  36354  1 sr_mod
sd_mod                 26313  5 
pata_acpi               3288  0 
ata_generic             3111  0 
ata_piix               21021  0 
ahci                   34897  4 
libata                152308  4 pata_acpi,ata_generic,ata_piix,ahci
scsi_mod               92676  4 sg,sr_mod,sd_mod,libata
             total       used       free     shared    buffers     cached
Mem:       2056944     590028    1466916          0      53232     207324
-/+ buffers/cache:     329472    1727472
Swap:      2313352          0    2313352
success.
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: not applicable.
/etc/pm/sleep.d/50-hdparm_pm suspend suspend: success.
/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
/usr/lib/pm-utils/sleep.d/95led suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend suspend: success.
/usr/lib/pm-utils/sleep.d/99video suspend suspend: kernel.acpi_video_flags = 0
success.
Mon Mar  8 15:46:24 WET 2010: performing suspend
***/usr/lib/pm-utils/pm-functions: line 259: echo: write error: Input/output error***
Mon Mar  8 15:46:32 WET 2010: Awake.
Mon Mar  8 15:46:32 WET 2010: Running hooks for resume
/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video resume suspend: success.
/usr/lib/pm-utils/sleep.d/95led resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
/usr/lib/pm-utils/sleep.d/90clock resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
/etc/pm/sleep.d/50-hdparm_pm resume suspend: success.
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg resume suspend: success.
/usr/lib/pm-utils/sleep.d/01grub resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
/usr/lib/pm-utils/sleep.d/00auto-quirk resume suspend: success.
Mon Mar  8 15:46:32 WET 2010: Finished.

Everything seems to be working fine, except after performing suspend. I have put *** in the edges of the relevant line to make it more noticable.
Issuing as root (sudo gives me a permission denied for some reason):

echo -n "mem" >/sys/power/state

results in the same error message:

bash: echo: write error: Input/output error

I've done a lot of googling, and couldn't find any relevant information.
Also, I don't really know when this started since it had been a while since I had last suspended my laptop.
Oh and also, suspend to disk never worked for me. But I'm not really worried about that. My boot time is short enough.

Thank you for any help you may provide!

Last edited by Stunts (2010-04-20 21:55:52)

Stunts · 2010-03-24 17:17:29

It's been a while... no ideas, anyone?
Not even that bash error?

lasu1 · 2010-04-20 21:49:05

Hmm....Odd, I got this error once (last night), after having successfully suspended the computer multiple times over the course of 10 days (10 days total uptime--average of two to three suspends).

After a reboot, the problem disappeared.

I have no clue what caused it, and unfortuneatly I cannot reproduce (it seems to be working now). I'll keep you posted, though, if it happens again.

Stunts · 2010-04-20 21:55:19

Wow!

Is this funny or what?
I also just tested suspend after not having tried it for quite a while (last time I testes was after upgrading to 2.6.33 - and it was still not working) and today it worked again!
Go figure! But thanks for posting.
I'll mark this thread solved, despite not knowing what caused it or solved it.

Last edited by Stunts (2010-04-20 21:56:38)

cowai · 2010-07-29 10:34:00

I got the same error. It occurred first a few days ago, after an update.

Yesterday my battery went dead under a kernel update! I could not boot my system (no, the fallback option didn't work). But who cares, a reinstall of Arch is just so fun! Really, I mean it

So now Arch is up, gnome is running, hal and everything is nice. Except suspend.

"/usr/lib/pm-utils/pm-functions: line 297: echo: write error: Device or resource busy" .

Line 297 in that file is:
do_suspend() { echo -n "mem" >/sys/power/state; }

Any help?

crabman · 2010-09-30 18:16:18

I have the same problem. Google didnt help me. Any ideas?

Stunts · 2010-09-30 18:38:14

The bad news is:
This seems to come and go, so it's kind of hard to reproduce.

The good news is:
This seems to come and so, and as such you will eventually get suspend back.

As a workaround, check the archwiki for alternate forms of suspend.
http://wiki.archlinux.org/index.php/Suspend_to_RAM

Good luck!

KerrickStaley · 2011-01-26 01:41:48

Please don't mark as solved issues that are not actually solved. It wastes people's time.

Stunts · 2011-01-26 15:24:08

It's solved for me. An update solved this issue. Do I know which package was responsible? No.
But fact is, it's solved. Whatever problem I was having was solved with an update since I did not change anything in my system during the time it went from non working to working.
In fact it has not been an issue since my last post.
If you have a similar issue your problem is clearly not the same as mine, so you should start your own thread for it, if you still require assistance, of course.

le grand fuzzy · 2011-02-09 21:35:30

I came across this issue with when I upgraded to one of the 2.6.36 kernels, and when I downgraded to the last 2.6.35 kernel the problem resolved itself, so it may be somehow a kernel issue. I haven't bothered retrying any of the later 2.6.36 kernels yet.

C0NPAQ · 2014-06-13 12:58:13

WARNING: ISSUE NEVER SOLVED

Please just stop marking issues as SOLVED that were not solved at all, but instead just disappeared by sheer coincidence and arbitrariness for the initially reporting user. In such a case, the tag should be [INCONCLUSIVE] to be precise and helpful.

What happens otherwise is, that for every such thread, hundreds of people will google it the next 5+ years because they suffer from the same problem. Such a mistagged thread not only deceives those people and steals their time, because the problem was never solved as claimed, it also spams search results on google. Please just stop, all the time I get those spam results since years.

EDIT:

How I solved it:
Apparently my issue was caused by a module of some newly supported hardware I don't even use (tpm). Check dmesg and output on tty1 while doing the suspend. There should be a few or at least one warning/complaint about something. Then just rmmod that stuff and blacklist it.

Last edited by C0NPAQ (2014-06-13 13:32:55)

ewaller · 2014-06-13 14:57:25

Conpaq,

Welcome to Arch Linux. You have a valid point about marking things as solved when the problem just goes away, and the issues with polluting search results.
Consider, however, that the root cause of your issue may not be the same root cause that the original poster was fighting five years ago. We have been through dozens of kernels, deprecation of hal in favor of udev, systemd relacing our older init system, etc.... Your troubleshooting suggestion is spot on, but may be lost in that it is at the end of an ancient thread.

Your point is valid and falls under the "Version agnostic" clause in our policy with regards to old posts. Nevertheless, I am going to go ahead and close this thread now. If you would like to continue the discussion, feel free to start a new thread and link back to this one.

Thanks.

Arch Linux

#1 2010-03-08 15:54:57

[SOLVED] Unable to initiate suspend to ram

#2 2010-03-24 17:17:29

Re: [SOLVED] Unable to initiate suspend to ram

#3 2010-04-20 21:49:05

Re: [SOLVED] Unable to initiate suspend to ram

#4 2010-04-20 21:55:19

Re: [SOLVED] Unable to initiate suspend to ram

#5 2010-07-29 10:34:00

Re: [SOLVED] Unable to initiate suspend to ram

#6 2010-09-30 18:16:18

Re: [SOLVED] Unable to initiate suspend to ram

#7 2010-09-30 18:38:14

Re: [SOLVED] Unable to initiate suspend to ram

#8 2011-01-26 01:41:48

Re: [SOLVED] Unable to initiate suspend to ram

#9 2011-01-26 15:24:08

Re: [SOLVED] Unable to initiate suspend to ram

#10 2011-02-09 21:35:30

Re: [SOLVED] Unable to initiate suspend to ram

#11 2014-06-13 12:58:13

Re: [SOLVED] Unable to initiate suspend to ram

#12 2014-06-13 14:57:25

Re: [SOLVED] Unable to initiate suspend to ram

Board footer