[SOLVED] After resume from suspend to RAM, system is slow / unstable

Hello,
I have come across some strangeness when trying to suspend my system.  The
computer is a lenovo U350.  I have read a lot of threads on these subjects,
but I never found one that quite matched the experiences I'm having, so I felt
compelled to make a new post.
Here's what's going on:  I boot into the terminal, and then run pm-suspend.
Within a few seconds, the computer goes to sleep, just as I had hoped.  The
problem is that my computer seems a little groggy when I wake it back up.
Usually, when running a command like ps aux | less, the screen fills up very
quickly.  After I resume from sleep, running ps aux | less is noticeably slow.
It takes a full second (+/- epsilon) to fill the screen.  Other symptoms: if I
suspend / resume in the terminal, and then start a window manager (KDE), the
graphics will be slow and choppy, and when I try to exit the window manager, I
usually end up having to perform the dreaded REISUB after getting stuck on a
blank screen with a non-blinking cursor in the upper left hand corner.
Suspend / resume from KDE will result in either the black, non-responsive
screen as soon as I try to resume, or in the choppy graphics, followed by the
non-responsive black screen when I log out.
I looked at the process list before and after, and noticed that when the
system is first resumed, there are around 50-60 additional kworker processes
running than when I put it to sleep.  I don't know if this is normal or not.
Also, hci0 has been killed, and a new hci0 process has taken its place.  The
same goes for one of the udevd processes.  About 40-50 of the kworker
processes finish after a few minutes, but this does not change the slowness of
ps aux | less, nor does it help with my window manager issues.
I ran a few (not so precise) performance tests before and after doing a
suspend, and got the same results (the test was just to compile some LaTeX,
which took about 4-5 seconds either way).
I examined the pm-suspend.log, and everything looked peachy.  All of the
hooks returned success for the suspend, as well as the resume.  I'm happy to
post this if needed.  I did not change any of the default settings for
pm-suspend.
Anyhow, I've read a lot of threads, and seen a lot of suggestions, e.g.:
https://bbs.archlinux.org/viewtopic.php?id=137682
https://bbs.archlinux.org/viewtopic.php?id=136292 (use vbetool?)
https://bbs.archlinux.org/viewtopic.php?id=126174 (suspend tons of modules?)
https://bbs.archlinux.org/viewtopic.php?id=131827 (hpet=disable ?)
However, I'm not that confident in any of them, since no one had quite the
same issue.  I was hoping that someone could point me in the right direction
before I start blindly walking through all the candidate fixes and risk
unleashing chaos into my system.  Many thanks in advance for your help.
Oh, and in case this post was not yet long enough, here is some system
information:
lspci:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
08:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
lsmod:
Module Size Used by
aes_x86_64 7508 3
cryptd 8309 0
aes_generic 26138 1 aes_x86_64
coretemp 5590 0
cpufreq_ondemand 6164 2
acpi_cpufreq 5877 1
mperf 1275 1 acpi_cpufreq
freq_table 2515 2 acpi_cpufreq,cpufreq_ondemand
arc4 1410 2
joydev 9895 0
snd_hda_codec_hdmi 24121 1
iwlwifi 248196 0
i915 420018 3
snd_hda_codec_conexant 47300 1
uvcvideo 64311 0
mac80211 228527 1 iwlwifi
videodev 82101 1 uvcvideo
snd_hda_intel 23375 0
snd_hda_codec 89389 3 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi
broadcom 7270 0
tg3 134884 0
ideapad_laptop 8534 0
snd_hwdep 6389 1 snd_hda_codec
snd_pcm 74780 3 snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi
snd_page_alloc 7153 2 snd_pcm,snd_hda_intel
snd_timer 19544 1 snd_pcm
snd 59214 7 snd_timer,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi
iTCO_wdt 11885 0
v4l2_compat_ioctl32 8316 1 videodev
i2c_i801 8187 0
i2c_algo_bit 5263 1 i915
drm_kms_helper 26137 1 i915
intel_agp 10904 1 i915
btusb 11385 0
cfg80211 172260 2 mac80211,iwlwifi
bluetooth 151999 1 btusb
sparse_keymap 3120 1 ideapad_laptop
soundcore 6210 1 snd
drm 188499 4 drm_kms_helper,i915
rfkill 15498 3 bluetooth,cfg80211,ideapad_laptop
serio_raw 4429 0
iTCO_vendor_support 1961 1 iTCO_wdt
media 10597 2 videodev,uvcvideo
psmouse 61311 0
libphy 16985 2 tg3,broadcom
i2c_core 20492 6 drm,drm_kms_helper,i2c_algo_bit,i2c_i801,videodev,i915
intel_gtt 14519 3 intel_agp,i915
pcspkr 1819 0
evdev 9530 8
thermal 7799 0
wmi 8475 0
battery 6453 0
ac 2344 0
video 11164 1 i915
button 4470 1 i915
processor 25582 3 acpi_cpufreq
ext4 420412 3
crc16 1359 2 ext4,bluetooth
jbd2 71499 1 ext4
mbcache 5881 1 ext4
sd_mod 28307 5
ahci 20037 4
libahci 19559 1 ahci
libata 166654 2 libahci,ahci
scsi_mod 133676 2 libata,sd_mod
uhci_hcd 23116 0
ehci_hcd 40698 0
usbcore 146113 5 ehci_hcd,uhci_hcd,btusb,uvcvideo
usb_common 954 1 usbcore
Last edited by wes (2012-04-06 21:34:43)

I did try reinstalling, actually.  But I did not think to remove the battery and the ram...  I'm very curious now: what is the rationale / intuition for that?  Or is it just that empirical evidence suggests this may be a good idea?
Anyhow, the reinstall by itself did not help.  I tried it out with a pretty bare-bones setup and had the same results.  Here are a few other things I noticed:
- After the suspend, one of the cores is always running at the maximum clock frequency, according to powertop (although, according to ps aux, no one is doing any work).
- Even if I ssh to a nearby machine, I get the same experience when running `ls`.  The screen fills very slowly.  That narrows things down a little bit, but I was already guessing it would be graphics-related.
I have also tried a few random kernel boot parameters after reading things online, but none of those worked, and several stopped the machine from booting at all.
Thanks for your help.

Similar Messages

  • System freeze after resume from suspend to RAM

    Hi,
    since quite a while (probably ever) I am unable to suspend my computer to RAM because everytime it freezes a few seconds after resuming, never to become alive again until a reboot. After some investigation, I managed to get kernel logs by taking a picture of my screen. The logs were not written to disk, hence I didn't see anything before. I had to write these by hand, I hope I didn't insert any mistakes:
    kernel: sas: Enter sas_scsi_recover_host busy: 2 failed: 2
    kernel: sas: trying to find task 0xfff880008b5b680
    kernel: sas: sas_scsi_find_task: aborting task 0xfff880008b5b680
    kernel: sas: sas_scsi_find_task: task 0xfff880008b5b680 is aborted
    kernel: sas: sas_eh_handle_sas_errors: task 0xfff880008b5b680 is aborted
    kernel: sas: trying to find task 0xffff8804606ccb40
    kernel: sas: sas_scsi_find_task: aborting task 0xffff8804606ccb40
    kernel: sas: sas_scsi_find_task: task 0xffff8804606ccb40 is aborted
    kernel: sas: sas_eh_handle_sas_errors: task 0xffff8804606ccb40 is aborted
    kernel: sas: ata7: end_device-0:0: cmd error handler
    kernel: sas: ata8: end_device-0:1: cmd error handler
    kernel: sas: ata7: end_device-0:0: dev error handler
    kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    kernel: ata7.00: failed command: READ VERIFY SECTOR(S)
    kernel: ata7.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
    res 40/00:48:a0:79:88/00:00:07:00:00/40 Emask 0x4 (timeout)
    kernel: ata7.00: status { DRDY }
    kernel: ata7: hard resetting link
    kernel: sas: ata8: end_device-0:1: dev error handler
    kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    kernel: ata8.00: failed command: READ VERIFY SECTOR(S)
    kernel: ata8.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    kernel: ata8.00: status { DRDY }
    kernel: ata8: hard resetting link
    This issue seems to be related to disk failures like bad sectors but I am quite sure, that my SSDs are in a good shape. I ran some SMART tests, they all turned out to be okay. Suspending from my dual-booted Windows works fine as well (although if the bad sector would be on the linux partition, it would probably not affect Windows).
    Here's my setup:
    $ lsblk -St
    NAME HCTL TYPE VENDOR MODEL REV TRAN NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE RA WSAME
    sda 1:0:0:0 disk ATA Corsair Force 3 2 sata sda 0 512 0 512 512 0 cfq 128 128 0B
    sdb 7:0:0:0 disk ST1000DM 003-9YN162 NDP3 usb sdb 0 512 0 512 512 1 cfq 128 128 0B
    sdc 0:0:0:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdc 0 512 0 512 512 0 cfq 128 128 0B
    sdd 0:0:1:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdd 0 512 0 512 512 0 cfq 128 128 0B
    sr0 2:0:0:0 rom TSSTcorp CDDVDW SH-222AL SB00 sata sr0 0 512 0 512 512 1 cfq 128 128 0B
    $ lsblk -f
    NAME FSTYPE LABEL UUID MOUNTPOINT
    sda
    ├─sda1 ntfs Recovery 567437B974379B27
    ├─sda2 vfat DC2D-099E /boot
    ├─sda3
    ├─sda4 ntfs FEBED982BED933BD
    ├─sda5 ext4 arch 41bad924-84a2-4e0a-9cd4-4ea723a2a5a3 /
    └─sda6 swap 793fb3c1-8bec-4023-a7c3-ee94eee2e67a [SWAP]
    sdb
    └─sdb1 ntfs HDDRIVE2GO 2212E50812E4E231
    sdc
    └─sdc1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
    └─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
    sdd
    └─sdd1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
    └─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
    I am not sure which one of the disks causes the freeze but I assume it's the revodrive because the logs talk about two drives. The Revodrive internally holds two drives, which are set up to operate in a RAID 0. Windows is installed on the Corsair drive, and has no access to the Revodrive. However, I used to run Windows on the Revodrive a few years ago, and it worked just fine.
    Another interesting thing is that when I try to test suspend to RAM, the system does not freeze, nor produce errors. This only happens if none is written to /sys/power/pm_test (which means no automated wake-up, no testing).
    Any ideas on how I could narrow down this issue? Thanks a lot!
    EDIT
    I just checked and confirmed that this issue is originating from the OCZ Revodrive:
    $ dmesg | grep ata7.00 | head
    [ 7.136432] ata7.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
    [ 7.136436] ata7.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
    [ 7.146442] ata7.00: configured for UDMA/133
    $ dmesg | grep ata8.00 | head
    [ 7.310018] ata8.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
    [ 7.310023] ata8.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
    [ 7.320022] ata8.00: configured for UDMA/133
    Last edited by tuttiarch (2015-01-31 15:54:29)

    Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
    And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
    Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...

  • Bus/io errors after resume from suspend to ram

    Something very strange happened today. When I woke my computer out of suspend today, the BIOS made a bad beep sound (once, high pitched, the error kind of), but booted anyways.
    After starting up, I tried starting programs like sonata, gnome-mplayer, but both failed with either an "io error" or "bus error". Strangly, I also tested "df" an it worked.
    That happened the first time, but I'm worried it's gonna happen again, because I have NO idea what could have failed.
    pm-suspend log looks fine
    Initial commandline parameters:
    Sa 27. Mär 02:30:54 CET 2010: Running hooks for suspend.
    /usr/lib/pm-utils/sleep.d/00auto-quirk suspend suspend: Adding quirks from HAL: --quirk-dpms-on --quirk-dpms-suspend --quirk-vbe-post --quirk-vbemode-restore --quirk-vbestate-restore --quirk-vga-mode-3
    success.
    /usr/lib/pm-utils/sleep.d/00logging suspend suspend: Linux segfault 2.6.32-ARCH #1 SMP PREEMPT Mon Mar 15 20:44:03 CET 2010 x86_64 AMD Phenom(tm) II X4 940 Processor AuthenticAMD GNU/Linux
    Module                  Size  Used by
    it87                   18948  0
    hwmon_vid               2756  1 it87
    ipv6                  283335  30
    nfs                   295530  0
    lockd                  65788  1 nfs
    fscache                39679  1 nfs
    nfs_acl                 2335  1 nfs
    auth_rpcgss            40448  1 nfs
    sunrpc                186318  5 nfs,lockd,nfs_acl,auth_rpcgss
    nvidia               9515743  48
    cryptd                  6076  0
    aes_x86_64              7420  1
    aes_generic            26178  1 aes_x86_64
    fuse                   58757  2
    joydev                  9800  0
    usbhid                 38471  0
    hid                    75813  1 usbhid
    arc4                    1354  2
    ecb                     1953  2
    snd_seq_dummy           1439  0
    snd_seq_oss            29023  0
    snd_seq_midi_event      5316  1 snd_seq_oss
    snd_seq                50558  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
    snd_seq_device          5181  3 snd_seq_dummy,snd_seq_oss,snd_seq
    snd_pcm_oss            39011  0
    snd_mixer_oss          17299  1 snd_pcm_oss
    nouveau               428060  0
    ttm                    46450  1 nouveau
    drm_kms_helper         23817  1 nouveau
    drm                   159774  3 nouveau,ttm,drm_kms_helper
    i2c_algo_bit            4935  1 nouveau
    snd_ctxfi              90523  1
    ath5k                 125370  0
    ohci_hcd               21485  0
    snd_pcm                70222  2 snd_pcm_oss,snd_ctxfi
    mac80211              166738  1 ath5k
    ath                     8400  1 ath5k
    snd_timer              18799  2 snd_seq,snd_pcm
    cfg80211              122783  3 ath5k,mac80211,ath
    rfkill                 15228  1 cfg80211
    edac_core              34056  0
    snd                    57408  10 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_ctxfi,snd_pcm,snd_timer
    soundcore               6095  1 snd
    snd_page_alloc          7033  2 snd_ctxfi,snd_pcm
    edac_mce_amd            6785  0
    led_class               2577  1 ath5k
    firewire_ohci          23601  0
    firewire_core          43019  1 firewire_ohci
    crc_itu_t               1273  1 firewire_core
    ppdev                   5910  0
    i2c_piix4               8680  0
    ehci_hcd               35082  0
    usbcore               140517  4 usbhid,ohci_hcd,ehci_hcd
    i2c_core               18137  6 nvidia,nouveau,drm_kms_helper,drm,i2c_algo_bit,i2c_piix4
    r8169                  36214  0
    mii                     3738  1 r8169
    parport_pc             31260  1
    button                  4714  1 nouveau
    thermal                11834  0
    evdev                   8825  10
    sg                     25275  0
    lp                      8684  0
    parport                29923  3 ppdev,parport_pc,lp
    pcspkr                  1795  0
    cpufreq_ondemand        8101  0
    powernow_k8            11886  0
    freq_table              2331  2 cpufreq_ondemand,powernow_k8
    processor              30310  1 powernow_k8
    rtc_cmos                8904  0
    rtc_core               14631  1 rtc_cmos
    rtc_lib                 1810  1 rtc_core
    ext3                  125021  2
    jbd                    46334  1 ext3
    mbcache                 5466  1 ext3
    sr_mod                 15043  0
    cdrom                  36354  1 sr_mod
    sd_mod                 26313  5
    pata_acpi               3288  0
    ata_generic             3111  0
    ahci                   34929  4
    pata_atiixp             3633  0
    floppy                 55998  0
    libata                152308  4 pata_acpi,ata_generic,ahci,pata_atiixp
    scsi_mod               92676  4 sg,sr_mod,sd_mod,libata
                 total       used       free     shared    buffers     cached
    Mem:       2056776    1645468     411308          0     590048     414652
    -/+ buffers/cache:     640768    1416008
    Swap:       522072       5776     516296
    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: :: default down    [BUSY]    [DONE]
    success.
    /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: not applicable.
    /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.
    Sa 27. Mär 02:30:56 CET 2010: performing suspend
    Any other useful log files to check out?
    I just put the system to sleep and woke it up again, no problem. I only notice that yesterday it took way longer than usual to go into sleep mode. Except for funky graphic patterns, all worked flawlessy now.
    What could cause bus and io errors after wakeup?
    Last edited by Sadface (2010-03-27 10:55:35)

    Yes, im using systemd. I tried also downgrading xf86-video-intel to a version from some weeks ago, with no result.
    PS: no difference between systemclt suspend or pm-suspend from comand line.ùù
    PS2: I tried fluxbox session and there was no flickering, so it had to be something kde-session related, and I found it: it was the image pile xscreensaver, just switching to another one solved my problem.
    Thanks for your interest, wonderwoofy!
    Update: nothing solved, it was just temporarly by case... same issue as before...
    Last edited by steff (2012-11-09 21:04:39)

  • System freeze after resume from suspend

    I am running arch for about 5 month now and I always had freezes after resuming from suspend (to ram - systemctl suspend) every once in a while (like once a week or less). The freezes increased massively over the last month or so and for about 2 weeks now it happens 95% of the times I resume from suspend.
    The monitor turns on and shows things exactly how I left them, but is completely unresponsible EXCEPT for I can switch to another TTY (Ctrl+Shift+F*), however I cannot type or do anything in it...
    It doesnt have anything to do with the X server as it also happens after I suspend from TTY (without any X running).
    I also checked journalctl -b -1 (shows previous boot, since I always have to hard-reset the system) but it doesnt show anything after:
    Mar 13 17:16:54 Ununhaswellium systemd-sleep[3624]: Suspending system...
    (the suspend event before resuming)
    Are there any log files that could give a hint on what exactly goes on after the resume?
    Im running the latest official 3.13.6-1 kernel and updated my BIOS to the latest beta version yesterday - didnt help either...
    Ive read pretty much every thread on the internet by now about freezes after resume from suspend but none really helped
    Last edited by CharlieBra7o (2014-03-15 09:58:51)

    Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
    And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
    Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...

  • Touchpad permanently not working after resuming from suspend

    I lost touchpad and trackpoint functionality after resuming from suspend on my ThinkPad E530 (3259CTO).
    Even after a complete power off (with the battery removed), the touchpad is detected but doesn't send any event, and the trackpoint is not detected.
    In Windows, in the UltraNav control panel, the touchpad is marked as enabled and cannot be disabled, the trackpoint is grayed.
    In Linux, I can see the difference is kernel traces when the driver is loaded.
    Before : psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00
    Now    : psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x0/0x0
    After looking at https://gerrit.chromium.org/gerrit/#/c/31105/ and Synaptics public documentation, I was able to get more information : the device status register (F01_RMI_Data0) is 0x45, which means the touchpad is in flash programming mode since there is a firmware CRC failure.
    It looks like http://code.google.com/p/chromium-os/issues/detail?id=24298, so it's probably not a Lenovo specific problem, but a bug in Synaptics firmware.
    Can Lenovo provide the firmware to flash like http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/X220-Touchpad-jumpy-response-when-used-with-90... which would hopefully make my touchpad working again ?
    The original firmware should work, but an updated one would be better, if it avoids losing the touchpad again later.

     I don't know why, but this made me think of the episode of the simpsons when home tries to get over 300 pounds so he can work from home.  When he tries to dial the phone he hist all the buttons and gets a recording that says "We're sorry, you're fingers are too fat. To obtain a special dialing wand, please mash the keypad now."
    BTW, sorry I can't help... but at least I am entertained easily.

  • No sound in Flash after resuming from suspend

    After I resume from a suspend or sleep there is no sound in Flash and there is no networking.
    The only way is to restart my browser to reestablish the sound.
    Is there a solution for this problem?
    Thanks.

    This does not happen with Firefox in Ubuntu, as an example. So something must be wrong somewhere.
    I can confirm this happens to me in Arch with Firefox 4.0b7 and Chromium 7.0.517.44. I noticed that after resuming from suspend, not only sound (in Flash) is missing, but Flash is behaving weirdly (YouTube video plays much faster) and CPU usage goes crazy without doing any particular action.
    Last edited by Niavlys (2010-12-05 23:34:30)

  • Pc doesn't resume from suspend to ram anymore (new 3.4.2 kernel)

    hi.
    I was using nouveau without problem and with the little trick of using acpi_os_name="Microsoft Windows NT" kernel parameter, I was able to suspend to ram from gnome, and resume the pc without problem
    Not anymore. Now, if I suspend to ram, the pc does not resume. It correctly wake up the dvd drive, the hard-drive, began to read stuff on the hdd but the led of the power button stays blinking and the screen is not waken up.
    I am thinking this is due to the update of nouveau and a new regression but this seems related to the bios or hardware. For example. If after the broken resume, I hold down 10 seconds the power button to power off, and press it again to power on, the led is still blinking and it does not boot. I need to power off by removing the power cord.
    Is it because I run (to test it) the nvida-173xx, and that did something to the graphic card ?
    Did anyone got similar problem with the new nouveau driver ?
    I tried to downgrade libgl, libdrm, libdrm-nouveau, nouveau-dri, xf86-video-nouveau and mesa but I still got the problem. so ?
    I have a geforce 8300 GS. the pc is an inspiron 531
    Last edited by solstice (2012-06-18 08:56:49)

    Probably I have the same issue with geforce GTS250.
    After upgrading to kernel 3.4.2 or so, my system doesn't resume from suspend, only black screen and cannot switch to other ttys.
    I first thought this problem be caused by the kernel, but downgrading nvidia to 295.53-2 solved this problem on kernel 3.4.3 so this likely is caused by nvidia 302.17.
    In my case there is something like error in pm-suspend.log when resume failed:
    Fri Jun 22 05:36:12 JST: Awake.
    Fri Jun 22 05:36:12 JST: Running hooks for resume
    Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:
    /usr/lib/pm-utils/sleep.d/99video resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:
    /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:
    /usr/lib/pm-utils/sleep.d/95led resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
    /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:
    /usr/lib/pm-utils/sleep.d/90clock resume suspend: success.
    Running hook /etc/pm/sleep.d/90alsa resume suspend:
    xcb_connection_has_error() returned true
    And curiously, if I had launched vlc media player before suspend, resume worked well even on nvidia 302.17.

  • Cannot connect to X server after resume from suspend

    Hello,
    i'm a happy user of arch and i3, one and only thing that is not working correctly is that sometimes after resume from sleep (closing the lid, and then opening) I am not able to start any programs. this happens about 50% of the time. when it happens i have to exit i3 and login again, and everything works ok then.
    I'd be grateful for any suggestion how can I debug and solve this problem.
    y
    Last edited by yemu (2014-04-09 08:53:12)

    the error was, after running xterm:
    No protocol specified
    xterm: Xt error: Can't open display: :0.0
    after running scrot
    No protocol specified
    giblib error: Can't open X display. It *is* running, yeah?
    after running firefox
    (process:2559): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
    No protocol specified
    No protocol specified
    Error: cannot open display: :0.0
    but I think I was able to fix the problem.
    when I was browsing the internet for solution, I stumbled upon an info about similar problem caused by the hostname set to localhost. I checked my system, and apparently I haven't set my host name during install, and it was still localhost, so I changed it. and after that I tried suspending several times, and the problem never occured. I'll test in upcoming days, and if it works I will change the thread title to [SOLVED].
    Last edited by yemu (2014-04-10 07:40:47)

  • [SOLVED] Cannot resume from suspend but hibernate works fine

    Please help me figuring out what can be the issues..
    I cannot resume from suspend while "sudo pm-hibernate" works fine..
    When I use "sudo pm-suspend", the system (samsung N210 netbook) goes to sleep and I can see the power light blinking as expected. But, when I try to resume the system from suspend by pressing the power button, the screen remains black with no HDD activity. Only thing I can see is the power LED on.
    After I do "sudo pm-suspend" and try to resume from suspend but fails. So, I do a HARD reboot and then this is the content of  /var/log/pm-suspend.log
    Initial commandline parameters:
    Thu Dec 16 12:00:27 IST 2010: Running hooks for suspend.
    Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
    Linux archlinux-N210 2.6.36-ARCH #1 SMP PREEMPT Fri Dec 10 20:32:37 CET 2010 x86_64 Intel(R) Atom(TM) CPU N450 @ 1.66GHz GenuineIntel GNU/Linux
    Module Size Used by
    dm_mod 66662 0
    rfcomm 34874 4
    sco 8828 2
    bnep 8726 2
    l2cap 42585 16 rfcomm,bnep
    ipv6 281833 24
    nls_utf8 1288 0
    cifs 242984 0
    fscache 39915 1 cifs
    fuse 64259 3
    arc4 1378 2
    snd_seq_dummy 1431 0
    snd_hda_codec_realtek 275887 1
    uvcvideo 61404 0
    videodev 64318 1 uvcvideo
    v4l1_compat 15578 2 uvcvideo,videodev
    ecb 2041 2
    snd_seq_oss 28760 0
    ath9k 80424 0
    joydev 10055 0
    btusb 11385 2
    v4l2_compat_ioctl32 10212 1 videodev
    bluetooth 52419 9 rfcomm,sco,bnep,l2cap,btusb
    snd_seq_midi_event 5436 1 snd_seq_oss
    mac80211 196159 1 ath9k
    ath9k_common 3624 1 ath9k
    ath9k_hw 290909 2 ath9k,ath9k_common
    snd_hda_intel 22285 1
    snd_hda_codec 79384 2 snd_hda_codec_realtek,snd_hda_intel
    ath 8822 2 ath9k,ath9k_hw
    snd_seq 50082 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
    snd_seq_device 5297 3 snd_seq_dummy,snd_seq_oss,snd_seq
    snd_pcm_oss 39221 0
    cfg80211 143110 3 ath9k,mac80211,ath
    snd_hwdep 6110 1 snd_hda_codec
    uhci_hcd 21926 0
    easy_slow_down_manager 3185 0
    snd_mixer_oss 17106 2 snd_pcm_oss
    snd_pcm 71921 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
    snd_timer 19265 2 snd_seq,snd_pcm
    cpufreq_powersave 958 0
    sky2 46293 0
    rfkill 15882 3 bluetooth,cfg80211
    led_class 2331 1 ath9k
    snd 57562 11 snd_hda_codec_realtek,snd_seq_oss,snd_hda_intel,snd_hda_codec,snd_seq,snd_seq_device,snd_pcm_oss,snd_hwdep,snd_mixer_oss,snd_pcm,snd_timer
    psmouse 52592 0
    cpufreq_ondemand 8215 2
    soundcore 5969 2 snd
    ehci_hcd 36988 0
    tpm_tis 7928 0
    shpchp 26453 0
    sg 25652 0
    phc_intel 9527 1
    battery 10231 0
    tpm 10957 1 tpm_tis
    samsung_backlight 2844 0
    serio_raw 4486 0
    snd_page_alloc 7249 2 snd_hda_intel,snd_pcm
    usbcore 137570 5 uvcvideo,btusb,uhci_hcd,ehci_hcd
    ac 3105 0
    pci_hotplug 24319 1 shpchp
    tpm_bios 5505 1 tpm
    i2c_i801 8550 0
    freq_table 2323 2 cpufreq_ondemand,phc_intel
    pcspkr 1819 0
    thermal 12242 0
    evdev 8519 14
    processor 25936 1 phc_intel
    mperf 1243 1 phc_intel
    ext4 313574 1
    mbcache 5722 1 ext4
    jbd2 69002 1 ext4
    crc16 1297 2 l2cap,ext4
    sd_mod 25856 4
    ahci 20353 3
    libahci 17982 1 ahci
    libata 156316 2 ahci,libahci
    scsi_mod 124891 3 sg,sd_mod,libata
    i915 321187 3
    drm_kms_helper 25963 1 i915
    drm 175314 3 i915,drm_kms_helper
    i2c_algo_bit 4911 1 i915
    button 4834 1 i915
    i2c_core 18726 6 videodev,i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit
    video 19305 1 i915
    output 1940 1 video
    intel_agp 29459 2 i915
    total used free shared buffers cached
    Mem: 2046212 603128 1443084 0 11400 258660
    -/+ buffers/cache: 333068 1713144
    Swap: 2250748 0 2250748
    /usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
    /usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
    /usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend:
    /usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend:
    /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
    Running hook /etc/pm/sleep.d/20_samsung-tools suspend suspend:
    /etc/pm/sleep.d/20_samsung-tools suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
    /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
    /usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
    /usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/91wicd suspend suspend:
    /usr/lib/pm-utils/sleep.d/91wicd suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
    /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
    /usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
    Kernel modesetting video driver detected, not using quirks.
    /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
    /usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
    Thu Dec 16 12:00:31 IST 2010: performing suspend
    Since, the last time I checked about suspend was 1.5 months back, I cant really make out as to what package caused the issue as I had a few upgrades since that time.
    I am no expert but it seems like it is the log of suspending the system, it seems like the system didnt even go to initial stage of resuming.
    Last edited by shadyabhi (2010-12-27 17:54:19)

    Well this is a long shot... But my laptop had some issues with suspending due to low-power governors preventing it from fully working at times.
    Because of that I manually suspend with the following script:
    #!/bin/bash
    clear
    cpufreq-set -g performance
    cpufreq-info
    echo "Continue? y/n? ";read bevestiging
    if [ $bevestiging = "y" ]
    then
    echo "System going down for suspension NOW!"
    pm-suspend
    else
    echo "Exiting..."
    exit 0
    fi
    exit 0
    All it really does in the end, is change the governer from which it's currently on to "performance", thus allowing maximum clock speed.
    I've also added in a little confirmation dialog to check whether it's properly switched.
    Of course, this will only work for you if you're also using laptop-mode and cpufrequtils.
    Edit: You need to run this script with sudo or as the root user.
    Last edited by Aeva (2010-12-16 14:16:32)

  • Desktop visible after resume (from suspend) and before screen is locke

    My desktop becomes visible for brief period (<1s) when the system resumes from suspended state. My desktop env. is XFCE4, it happens with both xscreensaver and gnome-screensaver (also with slimlock and i3lock), therefore I think it's not locker dependent. It's a major security flaw because sensitive information may be exposed (not just porn). Using both XFCE provided locking facilities (suspend/resume lock options in Power Manager and Session settings), and systemd suspend/resume hooks yields same result. I remember back then when I was using Gnome, I haven't had this issues. Does anyone have any idea how to prevent this desktop expose?

    Have you tried this --> https://wiki.archlinux.org/index.php/Pm … or_suspend ?

  • Dell Inspiron 7537 - Sound only works after resuming from suspend

    Hello,
    So my sound does not work after boot, only once I resume from suspend. So, once I turn on my computer, and I load sound, nothing work (everything is unmuted in Alsa) - then if I suspend my computer and resume - the sound works every time.
    I use Alsa and here is my amixer output (before and after suspend is the same) :
    eric@archlinux ~> amixer
    Simple mixer control 'Master',0
    Capabilities: pvolume pswitch pswitch-joined
    Playback channels: Front Left - Front Right
    Limits: Playback 0 - 65536
    Mono:
    Front Left: Playback 5358 [8%] [off]
    Front Right: Playback 5358 [8%] [off]
    Simple mixer control 'Capture',0
    Capabilities: cvolume cswitch cswitch-joined
    Capture channels: Front Left - Front Right
    Limits: Capture 0 - 65536
    Front Left: Capture 11003 [17%] [on]
    Front Right: Capture 11003 [17%] [on]
    What gets rebooted when I do a suspend, but not when I reboot? Does not seem to make sense to me.
    Thanks.

    Is there any additional information I can include to help figure this out?

  • No sound in flash after resume from suspend (linux debian)

    Using 10.0.r42, iceweael and linux 2.6.32 kernel.
    If I close the lid on my HP laptop which causes it to suspend, and the resume from suspend, other audio playing programs work, but I cant get any sound from iceweasel/flash until I kill all instances of iceweasel and restart the web browser.
    Is this a bug that is tied to flash?

    What a coincidence, mine is also from scratch.
    Good question about how sound is handled. ldd libflashplayer.so doen't give an answer.
    So somehow xulrunner can catch the sound.
    Libxpcom is linked to libasound. components/libmozgnome.so to libesd in my case.
    Maybe you can try fuser /dev/snd/* to identify which process is locking the device.

  • [SOLVED]No sound after resuming from suspend thinkpad t23

    On a T23 Thinkpad, suspend-to-ram works, but I have no sound and no network when resuming.
    After googling for a while, it seems I must unload sound modules before going to sleep and then reload my sound modules after resuming.
    lsmod|grep snd gives me this:
    snd_intel8x0 28700 3
    snd_ac97_codec 94756 1 snd_intel8x0
    snd_pcm_oss 38432 0
    snd_pcm 68996 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
    snd_timer 19332 1 snd_pcm
    snd_page_alloc 8072 2 snd_intel8x0,snd_pcm
    snd_mixer_oss 14464 1 snd_pcm_oss
    snd 44388 12 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
    soundcore 6496 1 snd
    ac97_bus 2432 1 snd_ac97_codec
    However, from the command line, after
    modprobe -r snd_seq_oss snd_seq snd_seq_device snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_pcm snd_timer snd_mixer_oss
    I get:
    FATAL: Module snd_intel8x0 is in use.
    Even though I have no sound apps running.
    I am planning on putting the modprobe -r command in /etc/pm/sleep.d/whatever to unload and then another to reload the mods.
    Any help appreciated.
    Last edited by Misfit138 (2008-01-07 02:27:07)

    OK, solved it. Placed this in /etc/pm/sleep.d/11suspend
    #!/bin/sh
    mixers="Master PCM CD"
    for mixer in $mixers ; do
    /usr/bin/amixer -q sset $mixer mute
    /usr/bin/amixer -q sset $mixer unmute
    done
    Just mutes and unmutes master, PCM and cd channels. Works perfectly. suspend-to-ram and hibernate now work 100%.
    Thinkpads are so sweet.

  • [Solved] No sound after resuming from suspend

    After suspending and resuming I no longer have any sound output (through headphone jack or my laptop speaker). The laptop is a toshiba portege r835. I can't say how long this has been happening, since I've only tried to play any sounds after resuming recently.
    Searching the forums I found the following thread: https://bbs.archlinux.org/viewtopic.php?id=151001
    I haven't tried this because it isn't exactly the same problem, but mostly because I'm currently stuck on kernel 3.5.6 because of the sandy bridge power regression issues.
    Does anyone have any other ideas on how to possibly fix this problem?
    Thanks!!
    Last edited by twistedcubic (2012-12-31 22:20:20)

    Solved, sort of.
    I had some double suspend issue: I had set up suspend with systemd before using xfce and then after installing xfce I set my power settings so that the computer would suspend after shutting the lid, so I would have to open the lid, shut it, and then open it again for the computer to actually resume. After turning off the suspend setting in the xfce power manager, and just using the systemd suspend, the sound works fine on resume (both headphones and speakers)!

  • [SOLVED]pc freezes after resuming from suspend.

    When I upgraded kernel from linux-3.3.8-1 to linux-3.4.2-2 or later  , PC freezes after resuming.
    Monitor comes back and kde requires passward , but after few seconds , everything freezes.
    keyboard and mouse won't respond.
    There is no log after resuming.
    Is there anybody who have same trouble?
    CPU intel core i7 2600k
    MB asrock H67M-GE
    /var/log/pm-suspend.log
    Initial commandline parameters:
    Thu Jun 21 16:52:33 JST 2012: Running hooks for suspend.
    Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
    Linux myhost 3.4.3-1-ARCH #1 SMP PREEMPT Mon Jun 18 08:28:29 CEST 2012 x86_64 GNU/Linux
    Module Size Used by
    w83627ehf 31388 0
    hwmon_vid 3196 1 w83627ehf
    xt_hl 1369 6
    ip6t_rt 2112 3
    nf_conntrack_ipv6 6650 7
    nf_defrag_ipv6 6401 1 nf_conntrack_ipv6
    ipt_REJECT 2281 1
    xt_LOG 11975 9
    xt_limit 2041 12
    xt_tcpudp 2503 18
    xt_addrtype 2853 4
    xt_state 1295 14
    ip6table_filter 1396 1
    ip6_tables 18198 2 ip6table_filter,ip6t_rt
    nf_conntrack_netbios_ns 1077 0
    nf_conntrack_broadcast 1285 1 nf_conntrack_netbios_ns
    nf_nat_ftp 1668 0
    nf_nat 15100 1 nf_nat_ftp
    nf_conntrack_ipv4 6871 9 nf_nat
    nf_defrag_ipv4 1339 1 nf_conntrack_ipv4
    nf_conntrack_ftp 6261 1 nf_nat_ftp
    nf_conntrack 61584 8 nf_nat_ftp,nf_conntrack_netbios_ns,nf_nat,xt_state,nf_conntrack_broadcast,nf_conntrack_ftp,nf_conntrack_ipv4,nf_conntrack_ipv6
    iptable_filter 1456 1
    ip_tables 16946 1 iptable_filter
    x_tables 16954 12 ip6table_filter,xt_hl,ip_tables,xt_tcpudp,xt_limit,xt_state,xt_LOG,iptable_filter,ip6t_rt,ipt_REJECT,ip6_tables,xt_addrtype
    snd_hda_codec_hdmi 23672 1
    snd_hda_codec_realtek 60377 1
    vboxdrv 1792262 0
    acpi_cpufreq 5933 1
    aesni_intel 43154 0
    mperf 1267 1 acpi_cpufreq
    snd_hda_intel 24053 4
    aes_x86_64 7508 1 aesni_intel
    ppdev 5902 0
    aes_generic 26138 2 aesni_intel,aes_x86_64
    ghash_clmulni_intel 4237 0
    r8169 49354 0
    i915 438164 3
    video 11307 1 i915
    i2c_i801 8180 0
    i2c_algo_bit 5391 1 i915
    drm_kms_helper 33051 1 i915
    drm 208958 4 i915,drm_kms_helper
    parport_pc 30765 0
    intel_agp 10936 1 i915
    mei 32152 0
    psmouse 70792 0
    pcspkr 1899 0
    processor 26567 1 acpi_cpufreq
    evdev 9754 6
    button 4502 1 i915
    intel_gtt 14047 3 i915,intel_agp
    parport 31395 2 ppdev,parport_pc
    i2c_core 20369 5 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit
    serio_raw 4653 0
    cryptd 8741 2 ghash_clmulni_intel,aesni_intel
    coretemp 5654 0
    iTCO_wdt 12813 0
    mii 4123 1 r8169
    iTCO_vendor_support 1929 1 iTCO_wdt
    snd_hda_codec 94273 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
    crc32c_intel 1987 0
    snd_hwdep 6300 1 snd_hda_codec
    snd_pcm 74958 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
    snd_page_alloc 7217 2 snd_pcm,snd_hda_intel
    snd_timer 18966 2 snd_pcm
    snd 58997 13 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
    soundcore 5410 1 snd
    microcode 12185 0
    ext4 424175 2
    crc16 1359 1 ext4
    jbd2 73919 1 ext4
    mbcache 5977 1 ext4
    usbhid 36430 0
    hid 85285 1 usbhid
    ehci_hcd 41154 0
    usbcore 147533 3 ehci_hcd,usbhid
    usb_common 954 1 usbcore
    floppy 58615 0
    sr_mod 14823 0
    cdrom 35648 1 sr_mod
    sd_mod 29239 4
    ahci 20549 4
    libahci 20023 1 ahci
    libata 167611 2 ahci,libahci
    scsi_mod 132942 3 libata,sd_mod,sr_mod
    total used free shared buffers cached
    Mem: 7900332 743308 7157024 0 34932 257560
    -/+ buffers/cache: 450816 7449516
    Swap: 15359996 0 15359996
    /usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
    /usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
    /usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
    /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
    /usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
    Running hook /etc/pm/sleep.d/90alsa suspend suspend:
    /etc/pm/sleep.d/90alsa suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
    /usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
    /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
    /usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
    Kernel modesetting video driver detected, not using quirks.
    /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
    Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
    kernel.acpi_video_flags = 0
    /usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
    Thu Jun 21 16:52:33 JST 2012: performing suspend
    Last edited by remingtontonpon (2012-07-25 01:58:04)

    In my case, monitor freezes too.
    And I have only one PC, so i can't try ssh.
    I logged into runlevel3 and try
    sudo pm-suspend
    and it works fine. So it seems this trouble caused only in runlevel5.
    I also tried following command in runlevel5
    # echo freezer > /sys/power/pm_test
    # echo mem > /sys/power/state
    # echo devices > /sys/power/pm_test
    # echo mem > /sys/power/state
    # echo platform > /sys/power/pm_test
    # echo mem > /sys/power/state
    # echo processors > /sys/power/pm_test
    # echo mem > /sys/power/state
    # echo core > /sys/power/pm_test
    # echo mem > /sys/power/state
    Everything works fine but sudo pm-suspend failed.
    Last edited by remingtontonpon (2012-06-25 08:18:26)

Maybe you are looking for