Comment # 26 on bug 944978 from Alberto Zacchetti

(In reply to Takashi Iwai from comment #24)
> Thanks.  Can you get the kernel message at crashing by any chance?
> 
> If not, try enabling kdump.  Unfortunately, kdump package on Leap beta1
> doesn't work well as is for now (reported in boo#947816).  Try the following
> instead:
> 
> - Add kdump OBS repo:
>   # zypper ar obs://Kernel:/kdump/openSUSE_Factory kdump
> 
> - Install kdump and kexec-tools from that repo
>   # zypper in -r kdump kdump kexec-tools
> 
> - Install yast2-kdump package
>   # zypper in yast2-kdump
> 
> - Set up kdump via yast2 kdump.  Enable the kdump in the checkbox, then
> configure the memory size.  yast2-kdump asks some stupid values there.  Just
> ignore them, give 256 to low memory, and leave 0 to high memory.
> 
> - Try to enable magic sysrq.  Add the following line to
> /etc/sysctl.d/99-sysctl.conf:
> 
> kernel.sysrq = 1
> 
> - Reboot the system.  Check "systemctl status kdump" and see that it's
> loaded properly without error.
> 
> - Check whether kdump works.  You can trigger it via magic sysrq,
> Alt-SysRq-c key combination.  (sysrq key is sometimes print-screen key,
> often activated with Fn key on laptops.)
> 
>   If nothing happens (or just keeping freezing), something went wrong. 
> Usually it switches to the crash dump kernel after some seconds, then starts
> dumping verbosely.  When the dump worked, run "reboot -f" there.
> 
> - If you confirmed that kdump works, try to reboot again and load the wifi
> driver manually.  If the kernel panics, it should trigger kdump by itself.
> If nothing happens, try to do alt-sysrq-c combo to trigger kdump manually.
> 
> Once when you get the kdump, please attach the dmesg output found in the
> obtained crash directory to Bugzilla.

Ok, I installed kdump and I did everything you said, but when I try to copy
dmesg.txt somewhere in the filesystem, once rebooted the system, do not find
it. How should I do?