Bug 934140

Summary:	yast2-kdump writes wrong kernel parameter
Product:	[openSUSE] openSUSE Distribution	Reporter:	Dario Savella <dario>
Component:	YaST2	Assignee:	E-mail List <yast2-maintainers>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	mpluskal
Version:	13.2
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 13.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Dario Savella 2015-06-09 16:56:56 UTC

To investigate an issue with suspend/resume, I installed kdump and configured it using yast2-kdump.

After reboot and a (successful) crash, I could not find any dump in the selected directory.
When I double checked the boot command line I noticed the new option was:

 crashkernel=64M-:32M

instead of the expected:

 crashkernel=64M@32M

The wrong value is written for both GRUB_CMDLINE_LINUX_DEFAULT and GRUB_CMDLINE_LINUX_DEFAULT.

Comment 1 Dario Savella 2015-06-09 19:59:02 UTC

My apologies.

I was obviously looking at outdated/incomplete documentation.
The syntax used by yast2-kdump is correct.

At least... the kdump service now starts, getting it to write the dump will be my next problem.

Comment 2 Martin Pluskal 2015-06-09 20:02:47 UTC

You probably want to increase amount of memory available to crashkernel (see also boo#903280)

Comment 3 Dario Savella 2015-06-10 13:58:56 UTC

Indeed with more memory it does produce a dump.