[Bug 1160722] New: kdump fails to load
http://bugzilla.opensuse.org/show_bug.cgi?id=1160722 Bug ID: 1160722 Summary: kdump fails to load Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: opensuse@mike.franken.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Starting with the latest Tumbleweed snapshot 20200110 kdump fails to load. Not sure, what "Permission denied" means in this context. load.sh[1509]: kexec_load failed: Permission denied load.sh[1509]: entry = 0x4ace9c740 flags = 0x3e0001 load.sh[1509]: nr_segments = 8 load.sh[1509]: segment[0].buf = 0x1912d20 load.sh[1509]: segment[0].bufsz = 0x70 load.sh[1509]: segment[0].mem = 0x4a1000000 load.sh[1509]: segment[0].memsz = 0x1000 load.sh[1509]: segment[1].buf = 0x191ad60 load.sh[1509]: segment[1].bufsz = 0x168 load.sh[1509]: segment[1].mem = 0x4a1001000 load.sh[1509]: segment[1].memsz = 0x1000 load.sh[1509]: segment[2].buf = 0x7f151aeca010 load.sh[1509]: segment[2].bufsz = 0x140e00c load.sh[1509]: segment[2].mem = 0x4a85f1000 load.sh[1509]: segment[2].memsz = 0x140f000 load.sh[1509]: segment[3].buf = 0x7f151c2dd610 load.sh[1509]: segment[3].bufsz = 0x89aaf0 load.sh[1509]: segment[3].mem = 0x4a9a00000 load.sh[1509]: segment[3].memsz = 0x3350000 load.sh[1509]: segment[4].buf = 0x190c6c0 load.sh[1509]: segment[4].bufsz = 0x4826 load.sh[1509]: segment[4].mem = 0x4ace97000 load.sh[1509]: segment[4].memsz = 0x5000 load.sh[1509]: segment[5].buf = 0x1905310 load.sh[1509]: segment[5].bufsz = 0x70e0 load.sh[1509]: segment[5].mem = 0x4ace9c000 load.sh[1509]: segment[5].memsz = 0x9000 load.sh[1509]: segment[6].buf = 0x1903ff0 load.sh[1509]: segment[6].bufsz = 0xc00 load.sh[1509]: segment[6].mem = 0x4acea5000 load.sh[1509]: segment[6].memsz = 0x4000 load.sh[1509]: segment[7].buf = 0x7f151ae72010 load.sh[1509]: segment[7].bufsz = 0x57000 load.sh[1509]: segment[7].mem = 0x4acea9000 load.sh[1509]: segment[7].memsz = 0x57000 kernel: ima: impossible to appraise a kernel image without a file descriptor; try using kexec_fi le_load syscall. kdump[1879]: FAILED to load kdump kernel: /sbin/kexec -p /boot/vmlinuz-5.4.7-1-default --append= " quiet no_console_suspend consoleblank=0 systemd.log_target=kmsg log_buf_len=10M printk.devkmsg=on modprobe.blacklist=n vidia modprobe.blacklist=nvidia_uvm modprobe.blacklist=nvidia_drm modprobe.blacklist=nvidia_modeset modprobe.blacklist=n ouveau modprobe.blacklist=nv elevator=deadline sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory nokaslr numa=off irqpoll nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0 panic=1" --initrd=/boo t/initrd-5.4.7-1-default-kdump , Result: kexec_load failed: Permission denied entry = 0x4ace9c740 flags = 0x3e0001 nr_segments = 8 segment[0].buf = 0x1912d20 segment[0].bufsz = 0x70 segment[0].mem = 0x4a1000000 segment[0].memsz = 0x1000 segment[1].buf = 0x191ad60 segment[1].bufsz = 0x168 segment[1].mem = 0x4a1001000 segment[1].memsz = 0x1000 segment[2].buf = 0x7f151aeca010 segment[2].bufsz = 0x140e00c segment[2].mem = 0x4a85f1000 segment[2 systemd[1]: kdump.service: Main process exited, code=exited, status=255/EXCEPTION systemd[1]: kdump.service: Failed with result 'exit-code'. It succeeds at early startup, though: kdump[1578]: Loaded kdump kernel: /sbin/kexec -p /boot/vmlinuz-5.4.7-1-default --append=" quiet no_console_suspend consoleblank=0 systemd.log_target=kmsg log_buf_len=10M printk.devkmsg=on modprobe.blacklist=nvidia modprobe.blacklist=nvidia_uvm modprobe.blacklist=nvidia_drm modprobe.blacklist=nvidia_modeset modprobe.blacklist=nouveau modprobe.blacklist=nv elevator=deadline sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory nokaslr numa=off irqpoll nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0 panic=1" --initrd=/boot/initrd-5.4.7-1-default-kdump -s, Result: systemd[1]: Started Load kdump kernel early on startup. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1160722 http://bugzilla.opensuse.org/show_bug.cgi?id=1160722#c1 Petr Tesařík <ptesarik@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbohac@suse.com, | |ptesarik@suse.com Assignee|kernel-maintainers@forge.pr |ptesarik@suse.com |ovo.novell.com | --- Comment #1 from Petr Tesařík <ptesarik@suse.com> --- On a deeply technical level, there are two syscalls for loading a panic kernel: 1. kexec_load() - the older API, where most work is done in user space 2. kexec_file_load() - the newer API, where most work is done by the kernel Only the latter syscall allows signature verification (required e.g. when Secure Boot is active). It seems that the panic kernel now requires signature verification, but for some reason it is not attempted. I'll have to look into this in more detail. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1160722 http://bugzilla.opensuse.org/show_bug.cgi?id=1160722#c5 --- Comment #5 from Michael Hirmke <opensuse@mike.franken.de> --- Problem still eists with kernel-default-5.4.13-1.1.x86_64 and kdump-0.9.0-10.1.x86_64. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1160722 http://bugzilla.opensuse.org/show_bug.cgi?id=1160722#c6 Michael Pujos <pujos.michael@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pujos.michael@gmail.com --- Comment #6 from Michael Pujos <pujos.michael@gmail.com> --- Does is load after boot if you issue 'systemctl start kdump' ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1160722 http://bugzilla.opensuse.org/show_bug.cgi?id=1160722#c7 --- Comment #7 from Michael Hirmke <opensuse@mike.franken.de> --- Yes, it does. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1160722 http://bugzilla.opensuse.org/show_bug.cgi?id=1160722#c8 --- Comment #8 from Michael Pujos <pujos.michael@gmail.com> --- OK. Having the same issue here and manually starting the kdump service after boot has completed always work. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1160722 http://bugzilla.opensuse.org/show_bug.cgi?id=1160722#c9 Michael Hirmke <opensuse@mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Michael Hirmke <opensuse@mike.franken.de> --- Seems to work now. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com