http://bugzilla.novell.com/show_bug.cgi?id=567572 http://bugzilla.novell.com/show_bug.cgi?id=567572#c0 Summary: crashkernel reservation fails after kdump was setup with yast2-kdump Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bernhard@bwalle.de QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.6) Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6 I tried to setup kdump on openSUSE 11.2. The yast2-kdump module added following kernel parameter to my /boot/grub/menu.lst: crashkernel=256M-:128M@16M On reboot, the crashkernel reservation failed with the error "memory in use" in the kernel log. Looking at /proc/iomem, the reason is clear: 00100000-bfedffff : System RAM 01000000-0155e6d2 : Kernel code 0155e6d3-019bcdcf : Kernel data 01abc000-01c4bf6f : Kernel bss (0x01c4bf6f == 28M) Because 28M is larger than 16M, the memory is in use. The kernel is just too big. However, the solution is easy: Since http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdif... the kernel can detect the offset automatically the right offset. Since we use a relocatable kernel, the offset doesn't matter when loading the kernel. So my request is to simply remove the '@16M' offset for x86-64, and while we are at it, also for x86(-32). So after that change there should be no architecture with a fixed offset in the kernel command line any more. I know that kdump is not important for openSUSE, so the request is to change that for next release only (11.3 or whatever that means). (I hope the description of the problem is clear enough, without the "Steps to Reproduce", "Actual Results" and "Expected Results" magic). Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.