@harald As a kernel developer I recommend instead disabling suspend and reporting the bug ;-) Usually kernel oops is a potential memory corruption, which can by definition have undefined collateral effects.
E.g. do "rtcwake -s 15 -m mem" and dump dmesg contents to the bug report.
When it comes to disabling suspend, it seems that making "lid close" not do anything is particularly hard these days so I made this short screencast of it :-)
I tried all combinations, and for the reasons I have no idea of, both upower and logind configuration need to be edited.