Comment 22 for bug 490742

I've the issue also on a MacBookPro 11,1. It takes exactly 34,2 seconds for the system to wakeup.

Strangely dmesg says the wakeup started on second 1864 and ended on 1869 :

[ 1864.618554] smpboot: CPU 7 is now offline
[ 1864.636283] ACPI: Low-level resume complete
[ 1864.636333] PM: Restoring platform NVS memory
[ 1864.636769] Enabling non-boot CPUs ...
[ 1864.636816] x86: Booting SMP configuration:
[ 1864.636817] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 1864.656612] kvm: enabling virtualization on CPU1
[ 1864.659865] CPU1 is up
[ 1864.659887] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 1864.679312] kvm: enabling virtualization on CPU2
[ 1864.682465] CPU2 is up
[ 1864.682487] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 1864.701491] kvm: enabling virtualization on CPU3
[ 1864.704665] CPU3 is up
[ 1864.704688] smpboot: Booting Node 0 Processor 4 APIC 0x1
[ 1864.721098] kvm: enabling virtualization on CPU4
[ 1864.723347] CPU4 is up
[ 1864.723358] smpboot: Booting Node 0 Processor 5 APIC 0x3
[ 1864.739362] kvm: enabling virtualization on CPU5
[ 1864.741830] CPU5 is up
[ 1864.741843] smpboot: Booting Node 0 Processor 6 APIC 0x5
[ 1864.757884] kvm: enabling virtualization on CPU6
[ 1864.760320] CPU6 is up
[ 1864.760332] smpboot: Booting Node 0 Processor 7 APIC 0x7
[ 1864.776361] kvm: enabling virtualization on CPU7
[ 1864.778802] CPU7 is up
[ 1864.858736] ACPI: Waking up from system sleep state S3
[ 1866.949677] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[ 1866.989763] PM: noirq resume of devices complete after 75.824 msecs
[ 1866.989821] [drm] Found 128MB of eLLC
[ 1866.989873] PM: early resume of devices complete after 0.090 msecs
[ 1866.989935] mei_me 0000:00:16.0: irq 49 for MSI/MSI-X
[ 1866.990017] snd_hda_intel 0000:00:1b.0: irq 50 for MSI/MSI-X
[ 1866.990127] snd_hda_intel 0000:00:03.0: irq 51 for MSI/MSI-X
[ 1867.062100] bcm5974: bad trackpad package, length: 8
[ 1867.092123] bcm5974: bad trackpad package, length: 8
[ 1867.094129] bcm5974: bad trackpad package, length: 8
[ 1867.096131] bcm5974: bad trackpad package, length: 8
[ 1867.098131] bcm5974: bad trackpad package, length: 8
[ 1867.100136] bcm5974: bad trackpad package, length: 8
[ 1867.102123] bcm5974: bad trackpad package, length: 8
[ 1867.104125] bcm5974: bad trackpad package, length: 8
[ 1867.134150] bcm5974: bad trackpad package, length: 8
[ 1867.136155] bcm5974: bad trackpad package, length: 8
[ 1867.333884] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1867.334115] ata1.00: unexpected _GTF length (8)
[ 1867.334490] ata1.00: unexpected _GTF length (8)
[ 1867.334574] ata1.00: configured for UDMA/133
[ 1867.334644] sd 1:0:0:0: [sda] Starting disk
[ 1868.230507] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[ 1869.959232] pciehp 0000:00:1c.0:pcie04: Link Training Error occurs
[ 1869.959233] pciehp 0000:00:1c.0:pcie04: Failed to check link status
[ 1869.959619] PM: resume of devices complete after 2968.252 msecs
[ 1869.959784] PM: Finishing wakeup.
[ 1869.959785] Restarting tasks ... done.

So I've the impression that the bug may be before. I'm developer but never interested myself in the process of wakeup from RAM, is it something involving grub also ? Because it may be there that it happens and not linux itself. Or is it this ACPI low-level resume which takes long ?