http://bugzilla.suse.com/show_bug.cgi?id=990003 http://bugzilla.suse.com/show_bug.cgi?id=990003#c9 Michal Kubeček <mkubecek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #9 from Michal Kubeček <mkubecek@suse.com> --- Sorry for the delay, I thought I did write the comment already. As far as I can tell, there is no sign of problem in your kernel log. In the meantime, I learned that current openSUSE kernels are (unlike upstream ones) configured to after 90 seconds on panic. I'm afraid a kernel log from an actual crashed session would be needed. There are two basic ways to get it: 1. Setup a serial console. This is easier but it requires a (real) serial port which is rather rare on current hardware and a serial ("laplink") cable. You would also need another machine to watch the serial console (a USB to serial adapter can be used on that one). 2. Setup kdump as described e.g. on https://doc.opensuse.org/documentation/leap/tuning/html/book.sle.tuning/cha.... For a start, dmesg.txt file found in the directory with the dump which is something like /var/crash/2016-08-16-14:41 should give some indication what went wrong. The full dump (vmcore file) would give more complete information but it's rather big and you should be aware that it contains a complete snapshot of your system's memory at the moment of the crash. Please let me know if you want more detailed instructions on one of these options. -- You are receiving this mail because: You are on the CC list for the bug.