http://bugzilla.opensuse.org/show_bug.cgi?id=985741 http://bugzilla.opensuse.org/show_bug.cgi?id=985741#c9 --- Comment #9 from Efstathios Agrapidis --- Already disabled everything. If you didn't tell, I would never notice the typo. ;) ...Running something battery intensive now and waiting to see what happens. You will hear from me soon enough... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985741 http://bugzilla.opensuse.org/show_bug.cgi?id=985741#c11 --- Comment #11 from Efstathios Agrapidis --- Created attachment 692633 --> http://bugzilla.opensuse.org/attachment.cgi?id=692633&action=edit journal right after the machine woke up by itself -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985741 http://bugzilla.opensuse.org/show_bug.cgi?id=985741#c13 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kernel-maintainers@forge.pr | |ovo.novell.com Flags| |needinfo?(kernel-maintainer | |s@forge.provo.novell.com) --- Comment #13 from Dominique Leuenberger --- [26571.472203] ACPI : EC: EC stopped [26571.472205] PM: Saving platform NVS memory [26571.472489] Disabling non-boot CPUs ... [26571.472743] Broke affinity for irq 26 [26571.472746] Broke affinity for irq 27 [26571.473758] smpboot: CPU 1 is now offline => here we're down [26571.473962] ACPI: Low-level resume complete [26571.473962] ACPI : EC: EC started [26571.473962] PM: Restoring platform NVS memory [26571.473962] Enabling non-boot CPUs ... [26571.473962] x86: Booting SMP configuration: => and already booting again :( imho, this is not directly a GNOME issue (gnome only asks for the suspend after all) - but without more info WHAT wakes the machine up (seeing that everything in acpi/wakeup has been disabled) seems tricky. @Kernel maintainers: do you have any idea on how to debug that? Or do you, from the info provided so far, even deduce that this could be a kernel issue? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985741 http://bugzilla.opensuse.org/show_bug.cgi?id=985741#c15 --- Comment #15 from Efstathios Agrapidis --- Testing SLED 12 SP2 reveals the same problem. Something I noticed and found interesting about SLED is that it stays suspended for three maybe four seconds and then it wakes up by itself. First time it happened I was not sure if I accidentally hit a key, so I tested it a couple more times to confirm it. Leap however wakes up immediately after suspending. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985741 http://bugzilla.opensuse.org/show_bug.cgi?id=985741#c17 --- Comment #17 from Richard Brown --- (In reply to Bjørn Lie from comment #16)

sudo vi /etc/UPower/UPower.conf

CriticalPowerAction=HybridSleep ==>> CriticalPowerAction=Hibernate

sudo systemctl restart upower.service

Let system run out of juice. Does it still reboot?

I have a strong feeling a lenovo x1 I had in the past, was bios hardwired to wake up when reaching a certain low level of battery while suspended so that windows could then put it into hibernate.

This is confirmed on my ASUS i7 UX303LN as well as Stathis' ancient celeron compaq laptop So I don't think it's hardware related Still think the above is a good test, Stathis can you try it? :) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985741 http://bugzilla.opensuse.org/show_bug.cgi?id=985741#c18 --- Comment #18 from Efstathios Agrapidis --- (In reply to Richard Brown from comment #17)

(In reply to Bjørn Lie from comment #16)

...

sudo vi /etc/UPower/UPower.conf

CriticalPowerAction=HybridSleep ==>> CriticalPowerAction=Hibernate

sudo systemctl restart upower.service

Let system run out of juice. Does it still reboot?

I have a strong feeling a lenovo x1 I had in the past, was bios hardwired to wake up when reaching a certain low level of battery while suspended so that windows could then put it into hibernate.

This is confirmed on my ASUS i7 UX303LN as well as Stathis' ancient celeron compaq laptop

So I don't think it's hardware related

Still think the above is a good test, Stathis can you try it? :)

Done! This workaround works well. Still it doesn't solve the problem but it is a good workaround and could be used as an more appropriate setting for the upower service, until the bug is closed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985741 http://bugzilla.opensuse.org/show_bug.cgi?id=985741#c20 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(zaitor@opensuse.o | |rg) --- Comment #20 from Dominique Leuenberger --- (In reply to Bjørn Lie from comment #16)

sudo vi /etc/UPower/UPower.conf

CriticalPowerAction=HybridSleep ==>> CriticalPowerAction=Hibernate

Should we switch the default here then if this causes so much trouble? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985741 http://bugzilla.opensuse.org/show_bug.cgi?id=985741#c23 --- Comment #23 from Dominique Leuenberger --- (In reply to Bjørn Lie from comment #21)

I guess we could - hibernate should be "safer" than hybrid-sleep, even if we deviate from upstream then.

Package change submitted to Base:System (for TW) and 42.1:Update (42.2 will inherit it) I wonder if we should keep the bug around; so far the kernel-team did not react at all -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985741 http://bugzilla.opensuse.org/show_bug.cgi?id=985741#c24 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |astieger@suse.com --- Comment #24 from Andreas Stieger --- Released update for 42.1, please progress bug as you deem necessary. -- You are receiving this mail because: You are on the CC list for the bug.