Comment # 47 on bug 917411 from macias -

Today events:

* another freeze -- this ruins my theory of saturation, only 2 days difference

* and installation as you wrote:

> - Try the newer upstream kernel, available in OBS Kernel:stable
> repo. You have a better chance there, as often the bug has been
> already fixed in the upstream.

I already tried that kernel (3.19), but OK.

> - Enable kdump to get the crash vmcore and dmesg.  Install
> yast2-kdump, and enable kdump.  It might be that yast2 kdump module
> can't set the right kernel parameter.  In that case, edit
> /etc/default/grub manually and append a boot option like
> "crashkernel=256M".

Yast did everything automatically -- I have in total:
showopts apm=off noresume edd=off powersaved=off nohz=off highres=off
processor.max_cstate=1 nomodeset x11failsafe crashkernel=512M-:256M

>   After the crash, you'll get dmesg.txt in the crash dump directory
> (if you're lucky).

Well, it is not a crash, but we will see... I keep my fingers crossed ;-).