From: Jay Lan <jay.zen.lan@gmail.com>
To: kexec@lists.infradead.org
Cc: "jay.j.lan@nasa.gov" <jay.j.lan@nasa.gov>
Subject: kdump failed to load: /sys/firmware/edd does not exist
Date: Thu, 22 Dec 2016 17:12:12 -0800 [thread overview]
Message-ID: <345de9dc-d728-2c5c-5634-2e70c4c6e030@gmail.com> (raw)
Hi,
I encountered kdump load failure problem at SLES12 SP1 and SLES12 SP2.
The 'systemctl status kdump.service' returned:
tpfe2 /var/log # 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 Thu 2016-12-22 09:24:46
PST; 32min ago
Process: 18982 ExecStart=/lib/kdump/load.sh (code=exited,
status=1/FAILURE)
Main PID: 18982 (code=exited, status=1/FAILURE)
Dec 22 09:24:46 tpfe2 systemd[1]: kdump.service: main process exited,
code=...RE
Dec 22 09:24:46 tpfe2 systemd[1]: Failed to start Load kdump kernel on
startup.
Dec 22 09:24:46 tpfe2 systemd[1]: Unit kdump.service entered failed state.
Dec 22 09:24:46 tpfe2 load.sh[18982]: + logger -i -t kdump 'FAILED to
load ...OR
Dec 22 09:24:46 tpfe2 load.sh[18982]: kexec_file_load failed: Key was
rejec...e'
Dec 22 09:24:46 tpfe2 load.sh[18982]: + return 1
Dec 22 09:24:46 tpfe2 load.sh[18982]: + result=1
Dec 22 09:24:46 tpfe2 load.sh[18982]: + '[' 1 = 0 ']'
Hint: Some lines were ellipsized, use -l to show in full.
When I ran '/sbin/kexec -d -p ...', the only suspicious output line was:
/sys/firmware/edd does not exist.
The kexec cmdline is:
# /sbin/kexec -d -p /boot/vmlinuz-3.12.62-60.64.8.2.20161026-nasa
--append="MAC=60:eb:69:21:2c:00 ROOTFS=disk IMAGE_PENDING=0
IMAGE=pfe-160901 SLOT=1 console=ttyS0,38400n8 MONITOR_CONSOLE=yes
intel_idle.max_cstate=1 processor.max_cstate=1 TRANSPORT=udpcast TTL=1
MCAST_RDV_ADDR=224.0.0.1 FLAMETHROWER_DIRECTORY_PORTBASE=9000
START_TIMEOUT=30 RECEIVE_TIMEOUT=5 elevator=deadline sysrq=yes
reset_devices acpi_no_memhotplug cgroup_disable=memory irqpoll nr_cpus=1
root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0
panic=1" --initrd=/boot/initrd-3.12.62-60.64.8.2.20161026-nasa-kdump
Could someone advise what might have caused /sys/firmware/edd not created?
The kexec-tools in SLES12 SP1 version is
kexec-tools-2.0.5-17.2.x86_64
I looked at sles11sp4 systems, the directory did exist.
Thanks in advance,
Jay
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2016-12-23 1:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=345de9dc-d728-2c5c-5634-2e70c4c6e030@gmail.com \
--to=jay.zen.lan@gmail.com \
--cc=jay.j.lan@nasa.gov \
--cc=kexec@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox