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

Similar Messages

  • [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)

  • 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)

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

  • Laptop screen doesn't wake up after suspend

    Basically the title is my problem. I've never had problems with suspending until a few days ago. When I close the lid, my laptop suspends as usual. But when I open it, the OS resumes but the screen remains black (no color/picture).  When I hit the power button after the OS is resumed, the screen activates and I can see the usual shutdown screen/lines. Does anyone know how to fix this problem?

    There are already a couple of threads about this already. Depending on your video card (Intel), it could be you just need to increase the brightness.
    In any event, please search before posting.

  • [Solved] Suspend to ram doesn't work correctly on Acer Aspire 5100

    Hi people of the archlinux forum.
    Finally I decided to change from ubuntu to archlinux because I wanted to learn more about the world of linux.:D
    I have already almost completely set up my laptop, but I have a problem when suspending to ram. The problem comes out when i wake up the laptop, and the screen starts to flicker and will not go away until i restart the laptop.
    This is my laptop after the suspend:
    I'm using pm-utils to suspend and hibernate my laptop, and the hibernate works fine. All settings were made following the arch wiki.
    this is my xorg.conf
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "dri"
    Load "extmod"
    Load "glx"
    Load "dbe"
    Load "dri2"
    Load "record"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    #DisplaySize 330 210 # mm
    Identifier "Monitor0"
    VendorName "AUO"
    ModelName "2174"
    EndSection
    Section "Device"
    ### Available Driver options are:-
    ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
    ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
    ### [arg]: arg optional
    #Option "NoAccel" # [<bool>]
    #Option "SWcursor" # [<bool>]
    #Option "Dac6Bit" # [<bool>]
    #Option "Dac8Bit" # [<bool>]
    #Option "BusType" # [<str>]
    #Option "CPPIOMode" # [<bool>]
    #Option "CPusecTimeout" # <i>
    #Option "AGPMode" # <i>
    #Option "AGPFastWrite" # [<bool>]
    #Option "AGPSize" # <i>
    #Option "GARTSize" # <i>
    #Option "RingSize" # <i>
    #Option "BufferSize" # <i>
    #Option "EnableDepthMoves" # [<bool>]
    #Option "EnablePageFlip" # [<bool>]
    #Option "NoBackBuffer" # [<bool>]
    #Option "DMAForXv" # [<bool>]
    #Option "FBTexPercent" # <i>
    #Option "DepthBits" # <i>
    #Option "PCIAPERSize" # <i>
    #Option "AccelDFS" # [<bool>]
    #Option "IgnoreEDID" # [<bool>]
    #Option "CustomEDID" # [<str>]
    #Option "DisplayPriority" # [<str>]
    #Option "PanelSize" # [<str>]
    #Option "ForceMinDotClock" # <freq>
    #Option "ColorTiling" # [<bool>]
    #Option "VideoKey" # <i>
    #Option "RageTheatreCrystal" # <i>
    #Option "RageTheatreTunerPort" # <i>
    #Option "RageTheatreCompositePort" # <i>
    #Option "RageTheatreSVideoPort" # <i>
    #Option "TunerType" # <i>
    #Option "RageTheatreMicrocPath" # <str>
    #Option "RageTheatreMicrocType" # <str>
    #Option "ScalerWidth" # <i>
    #Option "RenderAccel" # [<bool>]
    #Option "SubPixelOrder" # [<str>]
    #Option "ShowCache" # [<bool>]
    #Option "ClockGating" # [<bool>]
    #Option "VGAAccess" # [<bool>]
    #Option "ReverseDDC" # [<bool>]
    #Option "LVDSProbePLL" # [<bool>]
    #Option "AccelMethod" # <str>
    #Option "DRI" # [<bool>]
    #Option "ConnectorTable" # <str>
    #Option "DefaultConnectorTable" # [<bool>]
    #Option "DefaultTMDSPLL" # [<bool>]
    #Option "TVDACLoadDetect" # [<bool>]
    #Option "ForceTVOut" # [<bool>]
    #Option "TVStandard" # <str>
    #Option "IgnoreLidStatus" # [<bool>]
    #Option "DefaultTVDACAdj" # [<bool>]
    #Option "Int10" # [<bool>]
    #Option "EXAVSync" # [<bool>]
    #Option "ATOMTVOut" # [<bool>]
    #Option "R4xxATOM" # [<bool>]
    #Option "ForceLowPowerMode" # [<bool>]
    #Option "DynamicPM" # [<bool>]
    #Option "NewPLL" # [<bool>]
    #Option "ZaphodHeads" # <str>
    Identifier "Card0"
    Driver "radeon"
    VendorName "ATI Technologies Inc"
    BoardName "RS482 [Radeon Xpress 200M]"
    BusID "PCI:1:5:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    I know you maybe need more info, but i don't really know what do you need... please tell me what do you need and a post it!
    Sorry for my english this isn't my native languaje... Thanks you for all
    Last edited by geonunez (2010-07-08 20:19:09)

    I have the same problem with my Acer Aspire 5100 (video ATI Xpress1100).
    xorg.conf is not used. Turning KMS off doesn`t help.
    I have tried to use uswsusp, but it doesn`t help. s2ram -n output correctly identify my laptop, which means it is in "whitelist" and correct settings for this hardware is known. s2ram suspend works, but screen blinking after waking up remains the same.
    [Sydorenko@SLE ~]$ sudo s2ram -n
    Machine matched entry 17:
    sys_vendor = 'Acer *'
    sys_product = 'Aspire 5100 *'
    sys_version = ''
    bios_version = ''
    Fixes: 0x3 S3_BIOS S3_MODE
    This machine can be identified by:
    sys_vendor = "Acer "
    sys_product = "Aspire 5100 "
    sys_version = "V3.10A"
    bios_version = "V3.10A"
    See http://suspend.sf.net/s2ram-support.html for details.
    Last edited by SydMax (2010-06-06 16:53:50)

  • K8N Neo-FSR CPU fan at full throttle after wake up from S3 (Suspend to RAM)

    Hi,
    using either Core Center or BIOS' smart cpu fan control my cpu fan throttles down to less than 2000 RPM without system load. Fine! But after wake up from S3 (Suspend to RAM) power down the cpu fan runs forever at full throttle with about >5000 RPM, making lots of noise. So far I didn't succeed neither with BIOS settings nor using Core Center to gain fan control after S3 wake up. Since Core Center apparently shows up the cpu temperature correctly with less than 40 degrees Celsius this may be a BIOS 1.4 bug.
    Can someone please point me into the right direction? Yep, I did read the FAQ and already use board's search function :-)
    Falo

    addendum
    did some further testing. Apparently this doesn't happen if I wait at least a couple of minutes between shutdown to S3 and wake up. In this case fan control works as expected afterwards.
    Falo

  • Qosmio X70-A-12K doesn't wake up

    After a made an upgrade of BIOS to version 1.5, my qosmio doesn't wake up again. It shows me the first image with the slogan of Toshiba and next step it just doesn't go further. what should I do?
    +Message was edited: non-English language has been removed+

    To be honest it is not easy to say what is wrong there. I don't know if there is some problem with BIOS update.
    Have you tried to enter BIOS settings?
    What happen when you try to use F12 button at start-up? Is there some reaction?
    Please note: use English language only.

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

  • My MacBook Pro sometimes doesn't wake up from sleep mode

    Dear users, my MacBook Pro (model 5,1 - 15" Late 2008) is behaving oddly since I upgraded to OSX Lion. Sometimes, after going into sleep mode, it doesn't wake up. When I hit a key (space or enter), I see the login screen, but it's not possible to type my keyword. The only thing active is "the spinning beach ball of death", so I have to manually shut down my Mac and start over. This problem (and also other problems) did not happen in Snow Leopard. The only thing that changed in my Mac is the OS; other programs remain the same. I already tried reseting PRAM and SMC, and fixing disk errors. Thanks for your attention.

    try running a hardware test and see if you get an error code: http://docs.info.apple.com/article.html?path=Mac/10.7/en/mh35727.html

  • Macbook Air Haswell-doesn't wake up

    As mentioned in the title, literally, my Macbook Air doesn't wake up occasionally.
    Sometimes (3 or 4 times out of 3-50) when i close the lid of my notebook and open, nothing appears but  the black screen appears and only the light of the keyboard glows. No input(including trackpad and the keyboard) helps get out of the black screen and the only thing i should do is to turn the power of and turn it on again.
    It seems that some users using Macbook Air Haswell and some Macbook Pro models.  And some explains it happens because of chrome browser. I purchased this notebook about a week ago and I can get a new one by contacting Apple Store. Should I get a new one and see if it happens? or should i just restore my notebook and see if it happens again? It's quite confusing and frustrating.

    As Linc says, use the phone support, but you may find that Apple tell you a fix is in the pipeline. 
    There appears to be a glitch with current MBA's where, if it goes to sleep and you try to wake it immediately, it can freeze (search this forum for MBA won't wake from sleep, MBA crash to black screen and similar for loads of info - for example this massive thread https://discussions.apple.com/thread/5118135?start=0&tstart=0). Your description of what happens matches this picture exactly. Until Apple come up with a fix, you can either switch off sleep or resist the temptation to wake the MBA too quickly after it goes into sleep mode.
    Some of us (including me) found this unsatisfactory - particularly as Apple are taking a lot longer to find a solution than they originally claimed - and got a refund. In my case I put the money towards a retina MBP. 
    As for the Chrome issue, I do not and have never used Chrome but was plagued by the problem nevertheless.
    By all means get a replacement using the 14 day exchange, but you may well find that the new MBA does the same (this is what I did within the first 14 days and the replacement was no different).  If you decide the problem is unacceptable, you could consider a refund - then the choice is yours whether to wait, jump ship to a PC or get a different Mac.

  • A brand new Mac Pro doesn't wake up from sleep

    I got a new Mac Pro.
    It has an external SATA controller and a video card with NVIDIA Quadro 4000 chipset on it.
    It has a Snow Leopard installed.
    The problem it has is that it doesn't wake up once it goes to sleep, either by choosing "Sleep" menu item or by using "Energy Saving" setting.
    I notice some people mention a keyboard doesn't respond while his trackpad does. In my case, nothing works.
    I don't know if it is due to keyboard or a magic mouse. I tried to connect another wired mouse to the enclosure of the Mac Pro directly, but it did't cause Mac Pro wake up.
    By searching on Google, many people seem to have this problem, whether they have Mac Pro, MacBook Pro, and so on.
    Personally, I have a 17" PPC iMac, 13" MacBook with Core Duo 2, and have used MacBook Pro 17", but they didn't have this problem.
    I tried to reset the SMC, but it didn't help.
    Do anyone know what cause this problem and how to solve it?
    Is there any patch for this?
    Thank you.

    Does it sound like it's waking up but the monitor just doesn't display anything?
    I ask because if so, I'm experiencing the same problem.  I have a Quad-Core Mac Pro (no external devices) and if it goes to sleep I have difficulty getting it to display anything on the monitor after waking it up.  Now, I just recently hooked up an additional monitor (VGA) for dual display, and the funny thing is, that monitor will wake, but my main monitor won't. 
    Sometimes I get this error after boot-up too, where the computer will get to the login screen, but my main monitor is receiving no signal ("at least according to my monitor").
    If that's the same issue, then I'll post any success I find for you!
    Best,
    J

  • After 10.9.3 update monitor doesn't wake up from sleep

    I have an LCD connected to the Mac Mini via a mini-DP to DVI adapter and a video projector is connected directly at the HDMI.
    The LCD is the "main" screen while the projector is only switched on for watching TV or movies.
    My "Computer sleep" is set to "never" and "display sleep" to 15min.
    All was working well until I updated to 10.9.3 ...
    Now, when the LCD goes to sleep (projector is powered off) it doesn't wake up any more.
    The computer is running and it is responding to my key-presses etc. but the monitor remains in a coma.
    Powering the monitor off and on again resolves the issue, e.g. the display shows correctly.
    This is however only a temporary fix as it refuses to wake up  upon the next sleep...
    The monitor itself is fine, it works on other systems flawlessly, e.g. on an older Mini.
    Any ideas?
    I have already force-fed it with the combo-udate but that didn't help.

    My iphone 3GS does the same thing, not only does it suddenly fail to wake up from sleep. It just crashes and I have to do a hard reset. Today it just turned off when the ipod was playing I was a mile away from it and it was in airplane mode as well. I have restored from backup once and would dearly love to have it downgraded but that doesn't seem to be much of an option. My phone ran like a dream before the upgrade....now I hate to say it but its completely unreliable.
    With so many people experiencing the same problem it makes me wonder why there isn't a fix.

  • MacBook Doesn't Wake Up (when External FireWire Drives attached)

    Anybody else notice their MacBook not waking up from sleep when Fire Wire drives are attached, specifically through the FW port or the Express Card port.
    Granted, the MacBook wakes up 50% of the time in general with nothing attached...kind of a crap shoot.

    Hi, I have a macbook air for some time now. It works fine, starts reasonable fast and with one exception I'm pleased with it.If I closed the LID or press the on-off button the system sleeps. When I open the lid the next day (8 -12 hrs later) the system doesn't wake up. The log file which I presume is send to Apple did lead to a patch. I saw on the support site various conversations in respect to this issue with various results.
    I see that the problem of James even returned and was not reported to be resolved until now.
    In my log I have the following messages, "Sleep failure" of last few days. What should I do to resolve this, or is Apple delivering a patch for this?
    <Start log copy>
    17-09-14 03:14:01,755 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
    com.apple.message.signature: Capability Failure
    com.apple.message.summarize: YES
    Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
    17-09-14 09:24:37,960 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
    com.apple.message.signature: Platform Failure
    com.apple.message.summarize: YES
    Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
    20-09-14 03:31:14,288 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
    com.apple.message.signature: Capability Failure
    com.apple.message.summarize: YES
    Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
    20-09-14 09:56:41,453 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
    com.apple.message.signature: Platform Failure
    com.apple.message.summarize: YES
    Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
    <end log copy>
    regards, Roderick.

Maybe you are looking for

  • How to refernce the set in a implementation of java.util.AbstractSet?

    Hi, I have to extend abstract set and so I have to overwrite the add method. I want to use the provided equal function, to do the duplicate checking. But since the equal method takes only one parameter, I can't use an own collection class to manage t

  • What ribbon cable should I get for my 3rd drive?

    Hi, I just installed my 3rd hard disk drive in my 933MHZ(was 733) QuickSilver G4. I recently emailed a vendor asking: "Hello, I have a Mac 733 Quick Silver computer and I just installed my third hard disk drive. I need a 40 pin 4(for later) drive scs

  • 911   overlay transparency

    How do a make an overlay transparency to use in sports video to highlight a player. If anyone can help me please email me at [email protected]

  • KP26 : Activity Price Calculations mismatch

    Hi Gurus; My client is having some problem with Activity Price Calculations through T.code KP26. The Client didnu2019t have this issue before the upgrade to ECC 6.0. Client actually wants to make the price uniform for all the months. Please refer bel

  • 64-bit W7 install/side-by-side configuration is incorrect

    I have installed CS4 Extended and Lightroom 2 with W7 64-bit.  CS4 64-bit does not function and gives the error "side-by-side configuration is incorrect."  CS4 with what appears to be 32 bit works, and Lightroom 2 64 bit works (though does not connec