* v4.8: arm64 fix kexec
@ 2016-12-14 19:20 Matthias Brugger
2017-01-04 13:58 ` Greg Kroah-Hartman
0 siblings, 1 reply; 2+ messages in thread
From: Matthias Brugger @ 2016-12-14 19:20 UTC (permalink / raw)
To: stable; +Cc: Greg Kroah-Hartman, Geoff Levand, Mark Rutland
Hi all,
kexec on arm64 is broken in v4.8.y because in /proc/iomem "nomap"
regions, like UEFI runtime services code/data, are marked as "System RAM".
On seattle this leads to the fact, that kexec from kexec-tools loads the
kernel and the initrd in a memory region which should be ""reserved".
This breaks kexec on the system.
commit
e7cd190385d1 ("arm64: mark reserved memblock regions explicitly in iomem")
Fixes this and should be added to v4.8 stable tree.
Thanks,
Matthias
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: v4.8: arm64 fix kexec
2016-12-14 19:20 v4.8: arm64 fix kexec Matthias Brugger
@ 2017-01-04 13:58 ` Greg Kroah-Hartman
0 siblings, 0 replies; 2+ messages in thread
From: Greg Kroah-Hartman @ 2017-01-04 13:58 UTC (permalink / raw)
To: Matthias Brugger; +Cc: stable, Geoff Levand, Mark Rutland
On Wed, Dec 14, 2016 at 08:20:27PM +0100, Matthias Brugger wrote:
> Hi all,
>
> kexec on arm64 is broken in v4.8.y because in /proc/iomem "nomap" regions,
> like UEFI runtime services code/data, are marked as "System RAM".
> On seattle this leads to the fact, that kexec from kexec-tools loads the
> kernel and the initrd in a memory region which should be ""reserved". This
> breaks kexec on the system.
>
> commit
> e7cd190385d1 ("arm64: mark reserved memblock regions explicitly in iomem")
>
> Fixes this and should be added to v4.8 stable tree.
Now queued up, thanks.
greg k-h
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-01-04 13:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-12-14 19:20 v4.8: arm64 fix kexec Matthias Brugger
2017-01-04 13:58 ` Greg Kroah-Hartman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).