[SOLVED] Something automatically wakes PC from suspend to RAM

Hello,
for the last two days my desktop PC automatically and instantaneously wakes from suspend-to-RAM when I try to put it to sleep. I found https://bbs.archlinux.org/viewtopic.php?id=135543 and tried the script that solved the problem for the OP with no success.
Some info that might be relevant:
I have not made any hardware changes to my computer lately;
The only devices connected to my computer are the display (DVI) my TV (HDMI) and a mouse and keyboard and a router.
I use the stock Arch kernel and update regularly from a synced mirror in Norway;
I suspend my computer with
dbus-send --system --print-reply --dest="org.freedesktop.UPower" \
/org/freedesktop/UPower org.freedesktop.UPower.Suspend
All wake-up events like PCIe, mouse and keyboard are disabled in BIOS.
Does anybody experience these problems lately, or know if this is a known issue//bug?
Here is an exerpt from dmesg:
[ 507.682162] ehci_hcd 0000:00:12.2: remove, state 4
[ 507.682177] usb usb1: USB disconnect, device number 1
[ 507.682600] ehci_hcd 0000:00:12.2: USB bus 1 deregistered
[ 507.682668] ehci_hcd 0000:00:12.2: PCI INT B disabled
[ 507.682847] ehci_hcd 0000:00:13.2: remove, state 4
[ 507.682858] usb usb2: USB disconnect, device number 1
[ 507.683206] ehci_hcd 0000:00:13.2: USB bus 2 deregistered
[ 507.683260] ehci_hcd 0000:00:13.2: PCI INT B disabled
[ 507.687630] ohci_hcd 0000:00:12.0: remove, state 4
[ 507.687644] usb usb3: USB disconnect, device number 1
[ 507.688134] ohci_hcd 0000:00:12.0: USB bus 3 deregistered
[ 507.688170] ohci_hcd 0000:00:12.0: PCI INT A disabled
[ 507.688392] ohci_hcd 0000:00:12.1: remove, state 4
[ 507.688405] usb usb4: USB disconnect, device number 1
[ 507.688909] ohci_hcd 0000:00:12.1: USB bus 4 deregistered
[ 507.688936] ohci_hcd 0000:00:12.1: PCI INT A disabled
[ 507.689078] ohci_hcd 0000:00:13.0: remove, state 4
[ 507.689087] usb usb5: USB disconnect, device number 1
[ 507.689524] ohci_hcd 0000:00:13.0: USB bus 5 deregistered
[ 507.689549] ohci_hcd 0000:00:13.0: PCI INT A disabled
[ 507.689680] ohci_hcd 0000:00:13.1: remove, state 1
[ 507.689690] usb usb6: USB disconnect, device number 1
[ 507.689697] usb 6-2: USB disconnect, device number 2
[ 507.740528] ohci_hcd 0000:00:13.1: USB bus 6 deregistered
[ 507.740563] ohci_hcd 0000:00:13.1: PCI INT A disabled
[ 507.740762] ohci_hcd 0000:00:14.5: remove, state 4
[ 507.740772] usb usb7: USB disconnect, device number 1
[ 507.741335] ohci_hcd 0000:00:14.5: USB bus 7 deregistered
[ 507.776761] ohci_hcd 0000:00:14.5: PCI INT C disabled
[ 508.174446] PM: Syncing filesystems ... done.
[ 508.423666] PM: Preparing system for mem sleep
[ 508.766827] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 508.780005] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[ 508.793339] PM: Entering mem sleep
[ 508.793357] Suspending console(s) (use no_console_suspend to debug)
[ 508.793635] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
[ 508.793679] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 508.793696] sd 2:0:0:0: [sdb] Stopping disk
[ 508.793776] sd 0:0:0:0: [sda] Stopping disk
[ 508.801620] i8042 aux 00:09: wake-up capability disabled by ACPI
[ 508.801788] serial 00:08: disabled
[ 508.801791] serial 00:08: wake-up capability disabled by ACPI
[ 508.801821] [drm] nouveau 0000:03:00.0: Disabling fbcon acceleration...
[ 508.801824] [drm] nouveau 0000:03:00.0: Unpinning framebuffer(s)...
[ 508.801851] [drm] nouveau 0000:03:00.0: Evicting buffers...
[ 508.801971] pata_atiixp 0000:00:14.1: PCI INT A disabled
[ 508.802040] r8169 0000:02:00.0: eth0: link down
[ 508.804819] r8169 0000:02:00.0: eth0: link up
[ 508.856993] [drm] nouveau 0000:03:00.0: Idling channels...
[ 508.857226] [drm] nouveau 0000:03:00.0: Suspending GPU objects...
[ 508.903407] snd_hda_intel 0000:00:14.2: PCI INT A disabled
[ 509.653173] r8169 0000:02:00.0: eth0: link down
[ 509.991371] [drm] nouveau 0000:03:00.0: And we're gone!
[ 509.991397] nouveau 0000:03:00.0: PCI INT A disabled
[ 510.003349] PM: suspend of devices complete after 1209.834 msecs
[ 510.003501] r8169 0000:02:00.0: PME# enabled
[ 510.003509] pcieport 0000:00:06.0: wake-up capability enabled by ACPI
[ 510.016920] PM: late suspend of devices complete after 13.567 msecs
[ 510.017438] ACPI: Preparing to enter system sleep state S3
[ 510.046822] PM: Saving platform NVS memory
[ 510.046980] Disabling non-boot CPUs ...
[ 510.149983] CPU 1 is now offline
[ 510.253310] CPU 2 is now offline
[ 510.258098] CPU 3 is now offline
[ 510.258336] Extended CMOS year: 2000
[ 510.258336] ACPI: Low-level resume complete
[ 510.258336] PM: Restoring platform NVS memory
[ 510.258336] PCI-DMA: Resuming GART IOMMU
[ 510.258336] PCI-DMA: Restoring GART aperture settings
[ 510.258336] Extended CMOS year: 2000
[ 510.258336] Enabling non-boot CPUs ...
[ 510.293928] Booting Node 0 Processor 1 APIC 0x1
[ 510.293929] smpboot cpu 1: start_ip = 9a000
[ 510.048288] Calibrating delay loop (skipped) already calibrated this CPU
[ 510.048288] [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu
[ 510.048288] perf: IBS APIC setup failed on cpu #1
[ 510.048288] Switch to broadcast mode on CPU1
[ 510.430265] NMI watchdog enabled, takes one hw-pmu counter.
[ 510.433741] CPU1 is up
[ 510.440522] Booting Node 0 Processor 2 APIC 0x2
[ 510.440524] smpboot cpu 2: start_ip = 9a000
[ 510.151487] Calibrating delay loop (skipped) already calibrated this CPU
[ 510.151487] [Firmware Bug]: cpu 2, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu
[ 510.151487] perf: IBS APIC setup failed on cpu #2
[ 510.151487] Switch to broadcast mode on CPU2
[ 510.471839] NMI watchdog enabled, takes one hw-pmu counter.
[ 510.471978] CPU2 is up
[ 510.472048] Booting Node 0 Processor 3 APIC 0x3
[ 510.472049] smpboot cpu 3: start_ip = 9a000
[ 510.258093] Calibrating delay loop (skipped) already calibrated this CPU
[ 510.258093] [Firmware Bug]: cpu 3, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu
[ 510.258093] perf: IBS APIC setup failed on cpu #3
[ 510.258093] Switch to broadcast mode on CPU3
[ 510.503352] NMI watchdog enabled, takes one hw-pmu counter.
[ 510.503508] CPU3 is up
[ 510.507795] ACPI: Waking up from system sleep state S3
[ 510.596799] pcieport 0000:00:02.0: restoring config space at offset 0x1 (was 0x100107, writing 0x100507)
[ 510.596824] pcieport 0000:00:06.0: restoring config space at offset 0x1 (was 0x100107, writing 0x40100507)
[ 510.596845] ahci 0000:00:11.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
[ 510.596863] ahci 0000:00:11.0: restoring config space at offset 0x2 (was 0x1018f00, writing 0x1060100)
[ 510.596866] ahci 0000:00:11.0: restoring config space at offset 0x1 (was 0x2300107, writing 0x2300507)
[ 510.596895] ahci 0000:00:11.0: set SATA to AHCI mode
[ 510.597097] pata_atiixp 0000:00:14.1: restoring config space at offset 0x3 (was 0x0, writing 0x4000)
[ 510.597131] snd_hda_intel 0000:00:14.2: restoring config space at offset 0x1 (was 0x4100006, writing 0x4100002)
[ 510.597240] nouveau 0000:03:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
[ 510.597244] nouveau 0000:03:00.0: restoring config space at offset 0xc (was 0x0, writing 0xfafe0000)
[ 510.597249] nouveau 0000:03:00.0: restoring config space at offset 0x9 (was 0x1, writing 0xec01)
[ 510.597252] nouveau 0000:03:00.0: restoring config space at offset 0x7 (was 0x4, writing 0xf8000004)
[ 510.597256] nouveau 0000:03:00.0: restoring config space at offset 0x5 (was 0xc, writing 0xd000000c)
[ 510.597259] nouveau 0000:03:00.0: restoring config space at offset 0x4 (was 0x0, writing 0xfb000000)
[ 510.597262] nouveau 0000:03:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[ 510.597266] nouveau 0000:03:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100107)
[ 510.597300] r8169 0000:02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
[ 510.597306] r8169 0000:02:00.0: restoring config space at offset 0xc (was 0x0, writing 0xf7fc0000)
[ 510.597316] r8169 0000:02:00.0: restoring config space at offset 0x6 (was 0x4, writing 0xf7fff004)
[ 510.597322] r8169 0000:02:00.0: restoring config space at offset 0x4 (was 0x1, writing 0xd801)
[ 510.597326] r8169 0000:02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[ 510.597331] r8169 0000:02:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100507)
[ 510.597446] PM: early resume of devices complete after 0.696 msecs
[ 510.597533] pata_atiixp 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 510.597552] snd_hda_intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 510.597581] [drm] nouveau 0000:03:00.0: We're back, enabling device...
[ 510.597586] nouveau 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 510.597589] pcieport 0000:00:06.0: wake-up capability disabled by ACPI
[ 510.597594] nouveau 0000:03:00.0: setting latency timer to 64
[ 510.597599] sd 0:0:0:0: [sda] Starting disk
[ 510.597603] r8169 0000:02:00.0: PME# disabled
[ 510.597605] [drm] nouveau 0000:03:00.0: POSTing device...
[ 510.597607] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 0 at offset 0xC718
[ 510.597690] sd 2:0:0:0: [sdb] Starting disk
[ 510.598730] serial 00:08: activated
[ 510.598867] Extended CMOS year: 2000
[ 510.610107] r8169 0000:02:00.0: eth0: link down
[ 510.621123] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 1 at offset 0xCC63
[ 510.663986] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 2 at offset 0xDA58
[ 510.664015] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 3 at offset 0xDB56
[ 510.665114] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 4 at offset 0xDDBE
[ 510.665116] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table at offset 0xDE23
[ 510.685128] [drm] nouveau 0000:03:00.0: Restoring GPU objects...
[ 510.725417] [drm] nouveau 0000:03:00.0: Reinitialising engines...
[ 510.725785] [drm] nouveau 0000:03:00.0: Restoring mode...
[ 510.762015] ata5.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[ 510.762018] ata5.00: ACPI cmd ef/03:44:00:00:00:a0 (SET FEATURES) filtered out
[ 510.762020] ata5.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 510.773704] ata5.00: configured for UDMA/66
[ 510.916691] ata4: SATA link down (SStatus 0 SControl 300)
[ 510.916722] ata2: SATA link down (SStatus 0 SControl 300)
[ 511.883355] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 511.988643] ata1.00: configured for UDMA/133
[ 512.681052] r8169 0000:02:00.0: eth0: link up
[ 513.909989] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 513.920747] ata3.00: configured for UDMA/133
[ 513.943983] PM: resume of devices complete after 3346.516 msecs
[ 513.944116] PM: Finishing wakeup.
[ 513.944117] Restarting tasks ... done.
[ 515.507636] ehci_hcd 0000:00:12.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 515.507721] ehci_hcd 0000:00:12.2: EHCI Host Controller
[ 515.507789] ehci_hcd 0000:00:12.2: new USB bus registered, assigned bus number 1
[ 515.507806] ehci_hcd 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[ 515.507854] ehci_hcd 0000:00:12.2: debug port 1
[ 515.507883] ehci_hcd 0000:00:12.2: irq 17, io mem 0xf7efe800
[ 515.520050] ehci_hcd 0000:00:12.2: USB 2.0 started, EHCI 1.00
[ 515.520407] hub 1-0:1.0: USB hub found
[ 515.520417] hub 1-0:1.0: 6 ports detected
[ 515.533786] ehci_hcd 0000:00:13.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 515.533832] ehci_hcd 0000:00:13.2: EHCI Host Controller
[ 515.533861] ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 2
[ 515.533877] ehci_hcd 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[ 515.533922] ehci_hcd 0000:00:13.2: debug port 1
[ 515.533951] ehci_hcd 0000:00:13.2: irq 19, io mem 0xf7efec00
[ 515.543343] ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00
[ 515.543684] hub 2-0:1.0: USB hub found
[ 515.543694] hub 2-0:1.0: 6 ports detected
[ 515.560288] ohci_hcd 0000:00:12.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 515.560342] ohci_hcd 0000:00:12.0: OHCI Host Controller
[ 515.560371] ohci_hcd 0000:00:12.0: new USB bus registered, assigned bus number 3
[ 515.560410] ohci_hcd 0000:00:12.0: irq 16, io mem 0xf7ef6000
[ 515.617252] hub 3-0:1.0: USB hub found
[ 515.617260] hub 3-0:1.0: 3 ports detected
[ 515.643394] ohci_hcd 0000:00:12.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 515.643453] ohci_hcd 0000:00:12.1: OHCI Host Controller
[ 515.643484] ohci_hcd 0000:00:12.1: new USB bus registered, assigned bus number 4
[ 515.643527] ohci_hcd 0000:00:12.1: irq 16, io mem 0xf7ef7000
[ 515.701535] hub 4-0:1.0: USB hub found
[ 515.701550] hub 4-0:1.0: 3 ports detected
[ 515.713826] ohci_hcd 0000:00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 515.713884] ohci_hcd 0000:00:13.0: OHCI Host Controller
[ 515.713915] ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 5
[ 515.713956] ohci_hcd 0000:00:13.0: irq 18, io mem 0xf7efc000
[ 515.771259] hub 5-0:1.0: USB hub found
[ 515.771273] hub 5-0:1.0: 3 ports detected
[ 515.786918] ohci_hcd 0000:00:13.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 515.786977] ohci_hcd 0000:00:13.1: OHCI Host Controller
[ 515.787011] ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 6
[ 515.787052] ohci_hcd 0000:00:13.1: irq 18, io mem 0xf7efd000
[ 515.844392] hub 6-0:1.0: USB hub found
[ 515.844407] hub 6-0:1.0: 3 ports detected
[ 515.857126] ohci_hcd 0000:00:14.5: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 515.857157] ohci_hcd 0000:00:14.5: OHCI Host Controller
[ 515.857169] ohci_hcd 0000:00:14.5: new USB bus registered, assigned bus number 7
[ 515.857192] ohci_hcd 0000:00:14.5: irq 18, io mem 0xf7eff000
[ 515.915097] hub 7-0:1.0: USB hub found
[ 515.915111] hub 7-0:1.0: 2 ports detected
[ 516.065641] EXT4-fs (sdb2): re-mounted. Opts: commit=0
[ 516.089845] EXT4-fs (sdb4): re-mounted. Opts: commit=0
[ 516.296726] usb 6-2: new low-speed USB device number 2 using ohci_hcd
[ 516.465653] input: LITEON Technology USB Multimedia Keyboard as /devices/pci0000:00/0000:00:13.1/usb6/6-2/6-2:1.0/input/input6
[ 516.465885] generic-usb 0003:046D:C312.0002: input,hidraw0: USB HID v1.10 Keyboard [LITEON Technology USB Multimedia Keyboard] on usb-0000:00:13.1-2/input0
This output is what I get right after a wake-up using the helper script from the other thread.
Thank you for any help!
Last edited by mariusmeyer (2012-03-03 15:57:16)

I'll try changing some BIOS settings, thanks As of now, I can't test your suggestion regarding input devices and wake-up because it takes less then a second for the computer to auto-wake-up
Also, I doubt the keyboard sets this off, because the scripts unloads all USB modules before suspending. But the mouse (a PS/2) on the other hand...
EDIT: I found out that it was the network waking the computer After stopping the network daemon before suspending, I can suspend normally! On a side note, I can wake the computer by pressing a key on my keyboard, but I do not know whether I could before or not. Anyways, this is solved for me
Last edited by mariusmeyer (2012-03-03 15:56:52)

Similar Messages

X121e - Black screen after wake up from suspend to RAM

I am the owner of a ThinkPad X121e - Notebook Type 3051-5QG (AMD E350 Processor). After a BIOS - Update from 1.07 to 1.16 I have a problem to wake it up from the S3 - Suspend to RAM function.
The Notebook restarts and the fan is working but there is no beep and the screen stays black. There is no way to get it working except a complete hard shutdown pushing the on/off-Button.
Does anybody know the problem and has a solution? Or do I have to wait and hope for the next BIOS-Version to solve the problem? I would like to downgrade to 1.07 BIOS, but I am afraid that this is not possible.
Solved!
Go to Solution.

Since 2012-12-02 Lenovo has published an new Bios-Version 1.17 .
I installed the update today and the problem is gone. I hope there is no new bug in this Bios-Version, but up to now everything seems to work properly.

Wake up from suspend to ram *twice*

Hello!
I am running arch on my Asus M51Vr laptop. Whenever I suspend to RAM and try to resume (i.e. hit a key), the laptop wakes up (sometimes without even locking the screen), and after 3-5 seconds it goes back to sleep; if I hit a key again, it will wake up with the screen locked (as configured) and then proceed normally.
This issue appeared some time ago after an update (was not there after installing arch). I am not sure where to start with the search for a fix, could you please help me?
Thank you!

I actually do have that script:
[root@phoenix group2]# cat /usr/lib/pm-utils/sleep.d/99video
#!/bin/sh
# Copyright 2006-2007 Richard Hughes <[email protected]>
# Copyright 2007 Peter Jones <[email protected]>
# This program is free software; you can redistribute it and/or modify
# it under the terms of version 2 of the GNU General Public License as
# published by the Free Software Foundation.
# Handle video quirks. If you are having suspend/resume issues,
# troubleshooting using this hook is probably the best place to start.
# If it weren't for video card quirks, suspend/resume on Linux would be
# a whole lot more stable.
. "${PM_FUNCTIONS}"
for opt in $PM_CMDLINE; do
case "${opt##--quirk-}" in # just quirks, please
dpms-on) QUIRK_DPMS_ON="true" ;;
dpms-suspend) QUIRK_DPMS_SUSPEND="true" ;;
radeon-off) QUIRK_RADEON_OFF="true" ;;
reset-brightness) QUIRK_RESET_BRIGHTNESS="true" ;;
s3-bios) QUIRK_S3_BIOS="true" ;;
s3-mode) QUIRK_S3_MODE="true" ;;
vbe-post) QUIRK_VBE_POST="true" ;;
vbemode-restore) QUIRK_VBEMODE_RESTORE="true" ;;
vbestate-restore) QUIRK_VBESTATE_RESTORE="true" ;;
vga-mode-3) QUIRK_VGA_MODE_3="true" ;;
no-fb) QUIRK_NOFB="true" ;;
save-pci) QUIRK_SAVE_PCI="true" ;;
no-chvt) QUIRK_NO_CHVT="true" ;;
none) QUIRK_NONE="true" ;;
*) continue ;;
esac
done
reset_brightness()
for bl in /sys/class/backlight/* ; do
[ -f "$bl/brightness" ] || continue
BR="$(cat $bl/brightness)"
echo 0 > "$bl/brightness"
echo "$BR" > "$bl/brightness"
done
if command_exists vbetool; then
vbe() { vbetool "$@"; }
else
vbe() { echo "vbetool not installed!" 1>&2; return 1; }
fi
if command_exists radeontool; then
radeon() { radeontool "$@"; }
else
radeon() { echo "radeontool not found" 1>&2; return 1; }
fi
die_if_framebuffer()
[ -d "/sys/class/graphics/fb0" ] || return
echo "--quirk-no-fb passed, but system is using a framebuffer."
echo "Aborting."
exit 1
save_fbcon()
local con
for con in /sys/class/graphics/*/state; do
[ -f $con ] || continue
echo 1 >"${con}"
done
resume_fbcon()
local con
for con in /sys/class/graphics/*/state; do
[ -f $con ] || continue
echo 0 >"${con}"
done
maybe_chvt()
is_set "$QUIRK_NO_CHVT" && return
fgconsole |savestate console
chvt 63
maybe_deallocvt()
state_exists console || return 0
chvt $(restorestate console)
deallocvt 63
# Some tiny helper functions for quirk handling
quirk() { is_set "$1" && [ -z $QUIRK_NONE ]; }
# save/restore vbe state
vbe_savestate() { vbe vbestate save |savestate vbestate; }
vbe_restorestate() { restorestate vbestate |vbe vbestate restore; }
# save/restore the vbe mode
vbe_savemode() { vbe vbemode get |savestate vbemode; }
vbe_restoremode()
# this is a little mode complicated to handle special-casing mode 3.
local vbemode=$(restorestate vbemode)
if [ "$vbemode" = "3" ]; then
vbe vgamode set $vbemode
else
vbe vbemode set $vbemode
fi
# post the video card
vbe_post()
local rom="/var/run/video.rom"
# if we do not have a romfile, do not post with it.
[ -f "$rom" ] || unset rom
vbe post $rom
sleep 0.1
# turn critical bits of radeon cards off/on
radeon_off() { radeon dac off; radeon light off; }
radeon_on() { radeon dac on; radeon light on; }
# save and restore video card PCI config state
save_pci()
local pci="/sys/bus/pci/devices"
for dev in "${pci}"/*; do
[ -f "${dev}/class" ] || continue
[ $(cat "${dev}/class") = "0x030000" ] || continue
[ -f "${dev}/config" ] || continue
# it is a video card, it has a configuration. Save it.
savestate "pci_video_${dev##*/}" <${dev}/config
done
restore_pci()
local pci="/sys/bus/pci/devices"
for dev in "${pci}"/*; do
state_exists "pci_video_${dev##*/}" || continue
restorestate "pci_video_${dev##*/}" > "${dev}/config"
done
suspend_video()
# 0=nothing, 1=s3_bios, 2=s3_mode, 3=both
local acpi_flag=0
quirk "${QUIRK_S3_BIOS}" && acpi_flag=$(($acpi_flag + 1))
quirk "${QUIRK_S3_MODE}" && acpi_flag=$(($acpi_flag + 2))
sysctl -w kernel.acpi_video_flags=$acpi_flag
quirk "${QUIRK_NOFB}" && die_if_framebuffer
quirk "${QUIRK_VBESTATE_RESTORE}" && vbe_savestate
quirk "${QUIRK_VBEMODE_RESTORE}" && vbe_savemode
quirk "${QUIRK_RADEON_OFF}" && radeon_off
quirk "${QUIRK_SAVE_PCI}" && save_pci
quirk "${QUIRK_VGA_MODE_3}" && vbe vbemode set 3
quirk "${QUIRK_DPMS_SUSPEND}" && vbe dpms suspend
save_fbcon
resume_video()
# We might need to do one or many of these quirks
quirk "${QUIRK_SAVE_PCI}" && restore_pci
quirk "${QUIRK_VBE_POST}" && vbe_post
quirk "${QUIRK_VBESTATE_RESTORE}" && vbe_restorestate
quirk "${QUIRK_VBEMODE_RESTORE}" && vbe_restoremode
resume_fbcon # also should be handled by a quirk.
quirk "${QUIRK_RADEON_OFF}" && radeon_on
quirk "${QUIRK_DPMS_ON}" && vbe dpms on
quirk "${QUIRK_RESET_BRIGHTNESS}" && reset_brightness
return 0 # avoid spurious hook exit failure message.
help() {
echo # first echo makes it look nicer.
echo "Video quirk handler options:"
echo
echo " --quirk-dpms-on"
echo " --quirk-dpms-suspend"
echo " --quirk-radeon-off"
echo " --quirk-reset-brightness"
echo " --quirk-s3-bios"
echo " --quirk-s3-mode"
echo " --quirk-vbe-post"
echo " --quirk-vbemode-restore"
echo " --quirk-vbestate-restore"
echo " --quirk-vga-mode-3"
echo " --quirk-none"
case "$1" in
suspend) maybe_chvt; suspend_video ;;
hibernate) maybe_chvt
if is_set "$HIBERNATE_RESUME_POST_VIDEO"; then
suspend_video
fi
resume) resume_video; maybe_deallocvt;;
thaw)
if is_set "${HIBERNATE_RESUME_POST_VIDEO}"; then
resume_video
fi
maybe_deallocvt
help) help ;;
esac
I did not touch the configuration files (I am not responsible for what pacman might have done).

Start up from 'suspend to ram' no longer starts wireless

When I finish with my desktop work I usually suspend to ram since it allows for quick startup. After a recent system upgrade, returning from suspend to ram no longer activates the wireless connection. NetworkManager is running in the processes list, but doesn't seem to do anything. I have to turn the computer off completely and then on again to get it to work.
Anyone else experiencing this?

I had the same issue, but on Chakra, did you try systemctl restart NetworkManager? I think that solves it without a complete reboot.

[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.

Wake up from suspend

Hi.
I have a MSI k7n2 delta ILSR with AMD 2500+ and 512 megs of RAM.
The wake up after suspend is working fine when I use an XP installed with my old motherboard (soltek), I just simly change the mainboard. Then I reinstall the Xp with the newest nForce drivers, and the wake up is not work. Why? All the rest of config was the same!
There is some hidden option in XP? Or what?
Best Regards: Timpi

Hi,
Actually, If I'm reading you right you should really have really done a new XP install on your new motherboard!
Make sure the settings in Control Panel> Power Options are set correctly. It may also be a good idea to run through your board's BIOS settings too! Refer to your manual for relevant details!
Axel

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.

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...

Systemd crashes on wake after a suspend to RAM - IBM Thinkpad X40

The most visible symptoms are that the computer won't shut down (from the xfce4-session UI or from sudo poweroff) and the networking is disabled and won't re-enable. When systemd crashes and I try a sudo systemctl command, it says it can't connect to the socket. The computer is otherwise running fine.
It's particularly annoying because when systemd crashes when I wake the computer up after suspending to RAM, I can't shut it down properly. I have had to stop suspending to ram entirely for the time being.
Last edited by ewtoombs (2013-11-24 21:59:29)

The most visible symptoms are that the computer won't shut down (from the xfce4-session UI or from sudo poweroff) and the networking is disabled and won't re-enable. When systemd crashes and I try a sudo systemctl command, it says it can't connect to the socket. The computer is otherwise running fine.
It's particularly annoying because when systemd crashes when I wake the computer up after suspending to RAM, I can't shut it down properly. I have had to stop suspending to ram entirely for the time being.
Last edited by ewtoombs (2013-11-24 21:59:29)

Toshiba NB550 doesn't wake up on Suspend to Ram

Hi everybody,
I don't know what to do. I got the NB550D and installed Ubuntu 11.10 on it. I am really happy with the machine, but when I do a suspend to ram, the netbook won't wake up. I got a black screen, the LEDs are on, but no reaction on buttons or ALT+PRINT+rseinub. I figured out that the fglrx driver is not the Problem, because the Problem exists even when I start it from the console or use the default driver.
I also tried uswsusp and to debug pm-suspend with pm-trace, but the only thing i got was a match in main.c.
I really don't know where to search the problem. When I put it to sleep and wake up it immedially it works, but when the NB sleeps about a few minutes it crashes.
Please help me, I'm going nuts!
thank you
greets
manum

Hi there
It sounds really strange that you get different results when Suspending to Ram a short time compared to Suspending to Ram a longer time.
Are You certain that time really is a factor and that other reasons are not the cause?
I mean, let's say You did 10 suspend-to-RAM's with 5 seconds suspeded state - would the unit wake up perfectly all those 10 times?
And if You did the same and let the unit be suspended 5 minutes - would it fail 10 out of 10 times?
If the symptoms are that consequent I would suggest you
1: Check that you are up to date with all packages and are using a "clean" install.
2: check you got the latest BIOS
3: if You have the latest BIOS and are updated and clean, file a bug at Ubuntu Bugzilla.
BR
Tom

OCZ Vertex 2 fails to fully resume from suspend to RAM

I have installed an OCZ Vertex 2 60GB SSD in my laptop and I cannot resume normally from S3 using pm-suspend or any other method. It looks like / isn't remounting, however it does seem that home is remounting.
I have flashed the firmware to the latest. I tested suspend after a base install, with only acpi and hal (pm-utils being a dep for hal) and it failed.
Here is fstab, mtab, and fdisk -l. If any other information is needed let me know.
Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb8372fcd
Device Boot Start End Blocks Id System
/dev/sda1 2048 206847 102400 83 Linux
/dev/sda2 206848 21178367 10485760 83 Linux
/dev/sda3 21178368 117231407 48026520 83 Linux
proc /proc proc rw,relatime
sys /sys sysfs rw,relatime
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=502347,mode=755
/dev/disk/by-uuid/fd40337d-ed8a-4e76-be3f-aa09f5558998 / ext4 rw,noatime,barrier=1,data=ordered,discard
devpts /dev/pts devpts rw 0 0
shm /dev/shm tmpfs rw,nosuid,nodev 0 0
/dev/sda3 /home ext4 rw,noatime,discard 0 0
/dev/sda1 /boot ext2 rw 0 0
none /tmp tmpfs rw,nosuid,nodev,noatime,size=1000M,mode=1777 0 0
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=8f046367-0eec-410f-b3b5-0e298e065c5e /home ext4 defaults,noatime,discard 0 1
UUID=a6f6aa9a-e5d8-4763-ad75-0b0b6c549929 /boot ext2 defaults 0 1
UUID=fd40337d-ed8a-4e76-be3f-aa09f5558998 / ext4 defaults,noatime,discard 0 1
none /tmp tmpfs nodev,nosuid,noatime,size=1000M,mode=1777 0 0
Here are some errors after suspend:
http://img180.imageshack.us/f/fserror.jpg/
http://yfrog.com/izfserror2j
I've also been advised to try enter S1, however I'm not sure how to do that since power states don't seem to work like this anymore (since kernel 2.6):
#echo 1 > sleep
I'm very frustrated at this point and I will be extremely gracious for any advice on this problem

I just successfully suspended to RAM. I was redirecting the log file to text file to make sure it kept it.....here it is. I'm going to check it out further to see if a package update fixed it, or if it was simply dumb luck.
/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.
Mon Nov 1 19:35:30 CDT 2010: performing suspend
Initial commandline parameters:
Thu Nov 4 00:54:33 CDT 2010: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux l33tpc 2.6.36-ARCH #1 SMP PREEMPT Sun Oct 31 09:29:11 CET 2010 x86_64 Genuine Intel(R) CPU U7300 @ 1.30GHz GenuineIntel GNU/Linux
Module Size Used by
cryptd 6262 0
aes_x86_64 7412 1
aes_generic 26170 1 aes_x86_64
ipv6 281961 14
ext2 63599 1
usb_storage 42540 0
uvcvideo 61404 0
videodev 64318 1 uvcvideo
v4l1_compat 15578 2 uvcvideo,videodev
v4l2_compat_ioctl32 10212 1 videodev
arc4 1378 2
ecb 2041 2
snd_hda_codec_intelhdmi 10645 1
snd_hda_codec_realtek 275631 1
i915 320893 2
snd_seq_dummy 1431 0
ath9k 79976 0
snd_seq_oss 28760 0
joydev 10055 0
snd_seq_midi_event 5436 1 snd_seq_oss
snd_hda_intel 22253 0
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
uhci_hcd 21926 0
snd_hda_codec 79192 3 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel
mac80211 195924 1 ath9k
drm_kms_helper 25963 1 i915
snd_pcm_oss 39157 0
snd_mixer_oss 17106 1 snd_pcm_oss
ath9k_common 3496 1 ath9k
snd_hwdep 6110 1 snd_hda_codec
drm 175314 2 i915,drm_kms_helper
ath9k_hw 289341 2 ath9k,ath9k_common
snd_pcm 71921 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
ath 8822 2 ath9k,ath9k_hw
ehci_hcd 36860 0
i2c_algo_bit 4911 1 i915
asus_laptop 14243 0
i2c_core 18726 5 videodev,i915,drm_kms_helper,drm,i2c_algo_bit
sparse_keymap 2563 1 asus_laptop
snd_timer 19265 2 snd_seq,snd_pcm
ac 3105 0
vboxdrv 1740411 0
battery 10039 0
cfg80211 142886 3 ath9k,mac80211,ath
snd 57562 11 snd_hda_codec_realtek,snd_seq_oss,snd_seq,snd_hda_intel,snd_seq_device,snd_pcm_oss,snd_hda_codec,snd_hwdep,snd_mixer_oss,snd_pcm,snd_timer
atl1c 31532 0
video 19305 1 i915
iTCO_wdt 10669 0
sg 25652 0
processor 25936 2
rfkill 15882 2 asus_laptop,cfg80211
soundcore 5969 1 snd
psmouse 52592 0
output 1940 1 video
iTCO_vendor_support 1801 1 iTCO_wdt
thermal 12242 0
button 4834 1 i915
usbcore 137506 5 usb_storage,uvcvideo,uhci_hcd,ehci_hcd
evdev 8519 7
serio_raw 4486 0
intel_agp 29427 2 i915
led_class 2331 2 ath9k,asus_laptop
pcspkr 1819 0
snd_page_alloc 7249 2 snd_hda_intel,snd_pcm
ext4 313574 2
mbcache 5722 2 ext2,ext4
jbd2 69002 1 ext4
crc16 1297 1 ext4
sd_mod 25824 4
ahci 20353 3
libahci 17886 1 ahci
libata 156316 2 ahci,libahci
scsi_mod 124859 4 usb_storage,sg,sd_mod,libata
total used free shared buffers cached
Mem: 4020904 219844 3801060 0 22892 53336
-/+ buffers/cache: 143616 3877288
Swap: 0 0 0
/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/11netcfg suspend suspend:
/usr/lib/pm-utils/sleep.d/11netcfg 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/55NetworkManager suspend suspend:
Having NetworkManager put all interaces to sleep...Done.
/usr/lib/pm-utils/sleep.d/55NetworkManager 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:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Thu Nov 4 00:54:34 CDT 2010: performing suspend
Thu Nov 4 00:57:50 CDT 2010: Awake.
Thu Nov 4 00:57:50 CDT 2010: 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/91wicd resume suspend:
/usr/lib/pm-utils/sleep.d/91wicd 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 /usr/lib/pm-utils/sleep.d/75modules resume suspend:
Reloaded unloaded modules.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend:
Having NetworkManager wake interfaces back up...Done.
/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth resume suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg resume suspend:
/usr/lib/pm-utils/sleep.d/11netcfg resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub resume suspend:
/usr/lib/pm-utils/sleep.d/01grub resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave resume suspend:
/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00logging resume suspend:
/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
Thu Nov 4 00:57:52 CDT 2010: Finished.
It failed again. I have compared the logs and the last entry is :
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Thu Nov 4 01:24:45 CDT 2010: performing suspend
Last edited by DarksideEE7 (2010-11-04 07:29:06)

[solved] kernel 3.1.5 kills suspend to ram

Hello all,
since the update to kernel 3.1.5 my system is not able to suspend to ram anymore. I haven't tested suspend to disk yet but I fear the result will be the same. System goes down but the wake up process hangs with a black screen. Only hard reset (!) can get me out here. Can't even change to another tty with ctrl-alt-Fx
Harvey
Edit: Same with suspend to disk. System doesn't even switch off. Both suspends were working before.
Last edited by Harey (2012-01-04 11:29:43)

pedromj wrote:What is your system/hardware (x86/x86-64, brand, CPU model, video card)?
My system:
harvey@obelix ~ $ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1a.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.1 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.2 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.3 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB Universal Host Controller (rev 06)
00:1d.7 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 06)
01:00.0 VGA compatible controller: nVidia Corporation G84 [GeForce 8600 GT] (rev a1)
02:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 02)
02:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 02)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
3f:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
3f:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
3f:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
3f:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
3f:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
3f:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
3f:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
3f:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
3f:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
3f:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
3f:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)
My kernel line:
kernel /vmlinuz-linux_64 cryptdevice=/dev/sda5:root root=/dev/mapper/root ro vga=795 resume=/dev/mapper/swapDevice
To make this clear:
This configuration has been working perfectly until I upgraded to kernel 3.1.5.
Edit: I downgraded kernel 3.1.5 -> 3.1.4 and everything is working again. The new kernel definitely is to blame
Harvey
Last edited by Harey (2011-12-13 16:14:37)

Cannot resume from suspend to ram (fglrx)

Hello,
I have recently installed Catalyst drivers, instead of xf86-video-ati. I have laptop with PowerXPress(Intel/AMD hybrid graphics).
I can't resume after suspend to ram. System freezes with black screen, tty switching doesn't work and I have to shutdown by holding power button.
If I add "nomodeset" to GRUB, X fails to start. xorg.conf generated using "aticonfig --initial". Catalyst driver works fine.
DE/DM: KDE 4/kwin
Graphic cards: Intel HD Graphics 3000; AMD Radeon 7600M.
Laptop: HP pavillion g6 2004er.

Welcome to the forum!
Yes, some Lenovo employees do read and post to this forum. Mark is quite active, and several others post as well. In addition, there are lurkers who just read without making public comments although sometimes they ask the mod team to either gather more information or pass along advice.
However, here are the expectations of their participation from the Welcome message:
These communities have been created to provide a high quality atmosphere in which users of Lenovo products and services may share experiences and expertise. While members from Lenovo may participate at intervals to engage in the discussions and offer advice and suggestions, this forum is not designed as a dedicated and staffed support channel.
The bottom line is there's no guarantee that you will get an answer to a question here directly from Lenovo.
On the other hand, you just might! ;-)
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Jane
2015 X1 Carbon, ThinkPad Slate, T410s, X301, X200 Tablet, T60p, HP TouchPad, iPad Air 2, iPhone 5S, IdeaTab A2107A, Yoga Tablet, Yoga 3 Pro
I am not a Lenovo Employee.
I AM one of those crazy ThinkPad zealots!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!

Resume from suspend to ram fails (pm-utils)

Hi,
When I suspend to ram the computer seems to suspend normally, but the resume fails and it triggers a normal boot instead.
I'm on a Lenovo Thinkpad X60 laptop with the 2.6.30 kernel and gnome-power-manager (pm-utils).

Unfortunately, every laptop seems to have its own idiosyncrasies with this (not to mention differences in different users' setups---e.g., what devices are attached, what modules are loaded). So it takes some serious trial and error to figure out how to get this to work. All I can suggest is that you become intimately familiar with the wiki page, and with the HAL quirks site, and that you try to eliminate all the daemons and so on you can while still generating the problem (e.g., boot into a virtual console instead of gnome, if you're comfortable with that). Then start a process of trying different quirks as explained on those webpages. Take good notes so you don't lose track of which combinations of quirks show result in what behavior.
The HAL quirks site will also point you to what other users using your laptop, or similar laptops, found to work. But trial and error may still be necessary.

X121e randomly wake up from suspended status and real time clock error

Hi all
Previously I considered my x121e suffer from overheating issue and causes real time clock error (RTC). However, after more testing and investigation, I believe the problem is related to other hardware issues and I like to hear people opinion before sending the laptop back to Lenovo.
The machine goes into suspend status either pressing the power button or closing the lid from Windows7 (clean install) without problem. However, it would wake up itself randomly, "beep" twice and screen shows RTC and CMOS checksum error. This happen more often when I am holding the machine (i.e. some movement/vibration). I wonder:
- Is it the RTC battery problem, cause the RTC to wake up the machine?
- Other hardware failure?
The laptop has a clean OS installed/recovered. Latest 1.16 Bios installed. No USB or memory card attached. Ram replaced and not the cause.
Please advise
Howard

Hello,
I am unsure; you would have to contact Lenovo directly and find out how they handle this situation. They may want the ThinkPad X121e back so they can run thorough diagnostics on it, just in case the problem is something else. That way it gets fixed the first time.
Regards,
Aryeh Goretsky
I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
Deutsche Community Comunidad en Español Русскоязычное Сообщество

[SOLVED] Something automatically wakes PC from suspend to RAM

Similar Messages

Maybe you are looking for