Re: [PATCH] x86_64: setup saved_max_pfn correctly (kdump)

[Andi Kleen]

On Thu, Nov 02, 2006 at 10:19:34PM +0900, Magnus Damm wrote:
> x86_64: setup saved_max_pfn correctly
> 
> 2.6.19-rc4 has broken CONFIG_CRASH_DUMP support on x86_64. It is impossible 
> to read out the kernel contents from /proc/vmcore because saved_max_pfn is set
> to zero instead of the max_pfn value before the user map is setup.

Do you know what patch has broken it? 

Or did just nobody test crash dump at all since -rc* started?

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/