Comment # 22 on bug 810133 from Takashi Iwai

(In reply to Olav Reinert from comment #20)
> (In reply to Takashi Iwai from comment #14)
> > Instead of pm-suspend, could you try "systemctl suspend"?  If this works,
> > the code path via systemd should be OK.
> 
> "systemctl suspend" works fine. (Tested within GNOME desktop on Tumbleweed
> 20150612)
> 
> Furthermore, after suspending that way, and resuming, then closing the lid
> also works (similar to the behaviour described in comment #7). At least
> once, sometimes more - after a few successful suspend+resumes by lid
> close+open it crashes the same way as always.
>  
> > It's still strange, though, that logind.conf doesn't give any behavior
> > change.  At least, the behavior with lid switch on Linux console (not X)
> > should be managed by systemd-logind.
> > 
> > To be sure, could you check whether this is really properly tested, e.g. by
> > changing it to "poweroff".  Then now it should go to poweroff instead of
> > suspend.
> 
> I edited logind.conf and set "HandleLidSwitch=poweroff", and rebooted
> straight to multi-user (runlevel 3) instead of the GNOME desktop. Upon
> closing the lid, the machine crashed the usual way.

Hm, so the event doesn't look handled at all by systemd.

> After rebooting the same way, I retested "systemctl suspend", and it works.
> Then, after closing the lid, the computer powered off.

OK, then let's check how the lid event is dealt at all.

Try to boot with nomodeset boot option.  Then unload i915 module and unload
button module.  Now the kernel lid switch handling gets removed.

At this state, try to close the lid.  Does it happen anything?