[Bug 905090] New: FAILED to load kdump kernel:Could not find a free area of memory of 0x9f000 bytes... locate_hole failed
http://bugzilla.opensuse.org/show_bug.cgi?id=905090 Bug ID: 905090 Summary: FAILED to load kdump kernel:Could not find a free area of memory of 0x9f000 bytes... locate_hole failed Classification: openSUSE Product: openSUSE Factory Version: 201411* Hardware: i686 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: mpluskal@suse.com QA Contact: qa-bugs@suse.de CC: bernhard@bwalle.de, ptesarik@suse.com Found By: --- Blocker: --- On 32 bit opensuse factory, kdump seems not to work: # systemctl status kdump -l kdump.service - Load kdump kernel on startup Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled) Active: failed (Result: exit-code) since Wed 2014-11-12 12:56:56 CET; 30min ago Main PID: 629 (code=exited, status=1/FAILURE) Nov 12 12:55:55 lojza boot.kdump[629]: Loading kdump Nov 12 12:56:56 lojza boot.kdump[629]: Could not find a free area of memory of 0x9f000 bytes... Nov 12 12:56:56 lojza boot.kdump[629]: locate_hole failed Nov 12 12:56:56 lojza kdump[6879]: FAILED to load kdump kernel: /sbin/kexec -p /boot/vmlinuz-3.18.0-rc4-1.g1eac9b3-default --append="quiet nomodeset elevator=deadline sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory irqpoll nr_cpus=1 disable_cpu_apicid=0 panic=1" --initrd=/boot/initrd-3.18.0-rc4-1.g1eac9b3-default-kdump , Result: Could not find a free area of memory of 0x9f000 bytes... locate_hole failed Nov 12 12:56:56 lojza boot.kdump[629]: ..failed # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.18.0-rc4-1.g1eac9b3-default root=UUID=1218d888-7c3f-4063-8891-9698084a924e resume=/dev/sda1 splash=silent quiet showopts crashkernel=64M-:32M nomodeset -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905090
roberto angelino
http://bugzilla.opensuse.org/show_bug.cgi?id=905090
Martin Pluskal
Is this fix going to be released to 13.2?
This bug was specific to i586.
rangelino@w520:~> cat /etc/SuSE-release openSUSE 13.2 (x86_64) VERSION = 13.2 CODENAME = Harlequin # /etc/SuSE-release is deprecated and will be removed in the future, use /etc/os-release instead
rangelino@w520:~> uname -a Linux w520.tuttipazzo.com 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux
rangelino@w520:~> sudo systemctl status kdump.service kdump.service - Load kdump kernel on startup Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled) Active: failed (Result: exit-code) since Mon 2015-02-09 07:36:35 PST; 1 day 4h ago Process: 1289 ExecStart=/etc/init.d/boot.kdump start (code=exited, status=1/FAILURE) Main PID: 1289 (code=exited, status=1/FAILURE)
Feb 09 07:36:35 w520 boot.kdump[1289]: Loading kdump Feb 09 07:36:35 w520 boot.kdump[1289]: Could not find a free area of memory of 0xa9b000 bytes... Feb 09 07:36:35 w520 boot.kdump[1289]: locate_hole failed Feb 09 07:36:35 w520 boot.kdump[1289]: ..failed Feb 09 07:36:35 w520 systemd[1]: Failed to start Load kdump kernel on startup.
Could you check if you have enough memory allocated for kdump? If you have configured this via yast kdump, this might be reason for your issues as yast for some reason defaults to allocating only 32MB. Anyway please create separate report, as Tony already said issue solved here was i586 specific, while you are apparently running x86_64 system. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905090
--- Comment #9 from Tony Jones
Is this fix going to be released to 13.2?
This bug was specific to i586.
rangelino@w520:~> cat /etc/SuSE-release openSUSE 13.2 (x86_64) VERSION = 13.2 CODENAME = Harlequin # /etc/SuSE-release is deprecated and will be removed in the future, use /etc/os-release instead
rangelino@w520:~> uname -a Linux w520.tuttipazzo.com 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC 2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux
rangelino@w520:~> sudo systemctl status kdump.service kdump.service - Load kdump kernel on startup Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled) Active: failed (Result: exit-code) since Mon 2015-02-09 07:36:35 PST; 1 day 4h ago Process: 1289 ExecStart=/etc/init.d/boot.kdump start (code=exited, status=1/FAILURE) Main PID: 1289 (code=exited, status=1/FAILURE)
Feb 09 07:36:35 w520 boot.kdump[1289]: Loading kdump Feb 09 07:36:35 w520 boot.kdump[1289]: Could not find a free area of memory of 0xa9b000 bytes... Feb 09 07:36:35 w520 boot.kdump[1289]: locate_hole failed Feb 09 07:36:35 w520 boot.kdump[1289]: ..failed Feb 09 07:36:35 w520 systemd[1]: Failed to start Load kdump kernel on startup.
There are endless reasons why this error could be output, in this specific case it was a i586 specific bug due to data sizes. Your specific question was "Is this fix going to be released to 13.2?" which wouldn't be of any use in your situation. Please file a new bug. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905090
--- Comment #10 from roberto angelino
Could you check if you have enough memory allocated for kdump? If you have configured this via yast kdump, this might be reason for your issues as yast for some reason defaults to allocating only 32MB.
This was the cause of the failure. I doubled it to 64MB, rebooted and it loads fine: sudo systemctl status kdump.service root's password: kdump.service - Load kdump kernel on startup Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled) Active: active (exited) since Thu 2015-02-12 09:05:08 PST; 14min ago Process: 1298 ExecStart=/etc/init.d/boot.kdump start (code=exited, status=0/SUCCESS) Main PID: 1298 (code=exited, status=0/SUCCESS) CGroup: /system.slice/kdump.service Feb 12 09:04:55 w520 boot.kdump[1298]: Loading kdump Feb 12 09:05:08 w520.tuttipazzo.com boot.kdump[1298]: ..done Problem solved. Thanks!!!! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com