On 2025-01-13 Mon 15:17:49 -0800, Andrew Morton wrote:
> Thanks. Are you able to confirm that reverting 18d565ea95fe fixes things?
Actually no, reverting 18d565ea95fe553f442c5bbc5050415bab3c3fa4
("kexec_file: fix incorrect temp_start value in locate_mem_hole_top_down()")
on top of v6.13-rc7 does not fix the issue.
So this might not be the real culprit.
But I verified that 18d565ea95fe553f442c5bbc5050415bab3c3fa4 is affected
while 18d565ea95fe553f442c5bbc5050415bab3c3fa4~1 is not.
