Your message dated Tue, 28 Jun 2016 13:18:26 -0600
with message-id <[email protected]>
and subject line Bug#754288: fixed in jessie kernels
has caused the Debian Bug report #754288,
regarding /sbin/kexec: kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
754288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754288
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kexec-tools
Version: 1:2.0.4-1
Severity: important
File: /sbin/kexec
Dear Maintainer,
after creating my own kernel with CONFIG_RANDOMIZE_BASE=y (that's not a
debian default) I noticed that the system won't reboot using kexec.
I am getting a black screen/CPU will be halted. The machine will need a
power cycle.
# zgrep 'RANDOMIZE' /proc/config.gz
CONFIG_RANDOMIZE_BASE=y
CONFIG_RANDOMIZE_BASE_MAX_OFFSET=0x40000000
Recompiling the same kernel (I tried 3.4.11 and 3.15.4) without
CONFIG_RANDOMIZE_BASE
will make kexec work again.
I also tested upstream's kexec-tools v2.0.7 to see if this problem is fixed
already in a newer version but it isn't.
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages kexec-tools depends on:
ii debconf [debconf-2.0] 1.5.53
ii libc6 2.19-4
kexec-tools recommends no packages.
kexec-tools suggests no packages.
-- debconf information:
kexec-tools/use_grub_config: false
* kexec-tools/load_kexec: true
--- End Message ---
--- Begin Message ---
As reported in earlier update from Thomas, this was a kernel issue and
was fixed in jessie kernels. Thsi bug can be closed now.
--
Khalid
--- End Message ---
