Re: [PATCH] Fix for kexec reboot failing after multiple continued kexec reboots

From: Jesse Barnes <jbarnes_at_engr.sgi.com>
Date: 2004-11-18 11:08:00
On Wednesday, November 17, 2004 3:44 pm, Jesse Barnes wrote:
> It's dying in find_pernode_space.  The efi memmap, though trimmed, should
> be ok at this point, so I'm still trying to figure out what's going on in
> that routine.

Actually, it looks like the EFI memmap isn't the same between a regular boot
 and a kexec boot even though I'm not messing with it via mem= or anything.
I check it in find_pernode_space and though the start is the same, the
length isn't.  In the kexec kernel, the length that's passed in is much bigger
in fact.

Regular boot:
find_pernode_space(0000003003000000, 0000000011000000, 0): pernodesize = 33783808
found space at 0000003003000000

kexec boot:
find_pernode_space(0000003003000000, 0000000079000000, 0): pernodesize = 163840
found space at 0000003003000000

(the kexec kernel was configured for 2p, while the regular one was 512p, which
explains the difference in pernodesize requirements).  I think the kexec kernel
is corrupting all sorts of important memory since it thinks it's got pages that
it shouldn't be touching.

Thanks,
Jesse
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Wed Nov 17 19:16:26 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:32 EST