Comment # 23 on bug 1219522 from Edwin KM
The kdump tool does not seem to kick-in at boot time.

I configured kdump using yast:
  zypper install yast2-kdump
  yast2 kdump

It seems to work if i run the "s", "u", "c" pattern. I see the text and a
folder in /var/crash.

Restarted a couple of times to trigger a kernel panic. In such a case it just
hangs a minute or so. And reboots afterwards.

Also changed the boot default line in yast boot loader to hide the boot logo
(and acutally show the text).
  "splash=verbose
resume=/dev/disk/by-id/nvme-WDC_PC_SN720_SDAQNTW-512G-1001_184523424461-part6
crashkernel=353M,high crashkernel=72M,low"


These tests actually corrupted my desktop text file with notes. It was never
open at the "suc" test.
Created photo's of the panics. Not sure there is any pattern (but the output is
garbled anyway)
Thinking about a reinstall or throwing this thing in the bin.


You are receiving this mail because: