Comment # 5 on bug 960848 from Daniel Morris

(In reply to Takashi Iwai from comment #3)
> Don't forget to check whether kdump really works beforehand.  For example,
> try
>   echo c > /proc/sysrq-trigger
> YaST kdump setup tends to give a too tight memory.  In doubt, give enough
> memory in kdump setup.

Thanks for the warning! YaST2 had only assigned 116M, which was indeed too
small (16GiB installed). 256M finally worked.

I've been around the loop quite a few times - according to
https://activedoc.opensuse.org/book/opensuse-system-analysis-and-tuning-guide/chapter-18-kexec-and-kdump,
crashkernel=512M should have been correct, but that stopped the machine from
booting (somewhere around the USB/SCSI probing as btrfs was mounting on the SSD
- it would black screen and lock hard, and the only way to look at the trail
was videoing it on my mobile). 

I also tried complying with the warnings that crashkernel=Y@X, appending @16M
for the offset, but it whined that it couldn't reserve the memory for the kdump
service.

Fig 18.1 (YaST2 Kdump) ought to be updated, as it complicates things with a
throw back to the early nineties with low & high memory. Maybe I've just had an
easy life since then... :)


> > [drm:intel_opregion_init [i915]] *ERROR* No ACPI video bus found
> 
> This doesn't seem relevant.  The ACPI video control is for brightness,
> usually for laptops or AiO machines.

Its a simple desktop, bought to avoid having any dodgy graphics drivers after
the never-ending cycle of ATI pain before. 

Plasma is funny though, showing an empty battery gauge at the login screen,
later refreshing to full.

> In anyway, it'd be helpful to give more details of your machine, e.g. the 
> output of "hwinfo --all".

Please find attached.