http://bugzilla.suse.com/show_bug.cgi?id=973727 http://bugzilla.suse.com/show_bug.cgi?id=973727#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tchvatal@suse.com, | |tiwai@suse.com Flags| |needinfo?(tchvatal@suse.com | |) --- Comment #1 from Takashi Iwai --- Both messages should be irrelevant. The thinkpad_acpi one is about the thermal table, and shouldn't stop anything. i915 one is a known harmless message. Is the suspend action really triggered by systemd or whatever? And, you don't connect to a dock / monitor while closing the lid, right? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=973727 http://bugzilla.suse.com/show_bug.cgi?id=973727#c3 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tchvatal@suse.com | |) --- Comment #3 from Takashi Iwai --- (In reply to Tomáš Chvátal from comment #2)

(In reply to Takashi Iwai from comment #1)

...

Both messages should be irrelevant. The thinkpad_acpi one is about the thermal table, and shouldn't stop anything. i915 one is a known harmless message.

Is the suspend action really triggered by systemd or whatever? And, you don't connect to a dock / monitor while closing the lid, right?

Nothing was connected.

It triggers the suspend because I have to kill the process to be able to start it from commandline.

Which process did you have to kill? Also, where did the process stall? You can see it in /proc/$PID/stack, for example.

There is nothing much extra in the logs, the only at least error-ish looking line was this.

Actually now i trieed plugging it to the docking station and it aborted the suspend. Then the lid close suspend works.

When I unplug the laptop from the station and close the lid it does nothing.

Hm, so something about dock status check is blocked? If it's something in i915, it'd be helpful to track the kernel messages with drm.debug=0x0e boot option until the stall point. Also, to be sure, please check whether the problem persists with OBS Kernel:openSUSE-42.1 kernel package. If yes, also it'd be helpful to check whether kernel-vanilla has the same problem (on 4.1.15 and 4.1.20). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=973727 http://bugzilla.suse.com/show_bug.cgi?id=973727#c5 --- Comment #5 from Tomáš Chvátal --- Created attachment 671471 --> http://bugzilla.suse.com/attachment.cgi?id=671471&action=edit hwinfo output -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=973727 http://bugzilla.suse.com/show_bug.cgi?id=973727#c7 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Takashi Iwai --- A magic is better than unfixable :) Let's close this for now, and feel free to reopen if you see the issue again. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.