Comment 5 for bug 1420129

Revision history for this message
Morten F. Rasmussen (mofi) wrote :

The upstream kernel didn't solve the problem.

The 5min time out had exactly the same behavior.
I was this time playing music while closing the lid. The music was never interrupted and the light never went out of the screen. The kernel knows the lid has been closed:
[ 51.675694] systemd-logind[1376]: Lid closed.
[ 91.193062] systemd-logind[1376]: Lid opened.

I noticed now, that clicking on "Suspend" doesn't work perfect (as I mistakenly wrote in the last post):
it immediately wakes up / resumes (I will boot the ubuntu-kernel and test if it has the same behavior).
This is also seen from the dmesg output:
[ 238.968218] PM: Preparing system for mem sleep
[ 238.968347] Freezing user space processes ... (elapsed 0.001 seconds) done.
[...]
[ 239.456134] smpboot: CPU 6 is now offline
[ 239.456413] intel_pstate CPU 7 exiting
[ 239.456490] Broke affinity for irq 31
[ 239.456492] Broke affinity for irq 34
[ 239.457497] kvm: disabling virtualization on CPU7
[ 239.457499] smpboot: CPU 7 is now offline
[ 239.474888] ACPI: Low-level resume complete
[ 239.474936] PM: Restoring platform NVS memory
[ 239.475324] Enabling non-boot CPUs ...
[ 239.475381] x86: Booting SMP configuration:
[ 239.475382] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 239.495644] kvm: enabling virtualization on CPU1
[ 239.536172] CPU1 is up
[ 239.547781] smpboot: Booting Node 0 Processor 2 APIC 0x4