Crash during vmcore_init

[Américo Wang]

On Wed, Nov 16, 2011 at 9:19 PM, Tim Hartrick <tim at edgecast.com> wrote:
> America,
>
> To clarify, crashkernel=480 at 2G or @1G doesn"t work either.  Further, for
> older kernels (2.6.32) it was possible to create crashkernel areas larger
> than 480M (crashkernel=512M).  Starting somewhere around 2.6.36, this
> stopped working.  Are you saying this was an intentional change?
>

No, I am not saying this.

Depends on your machine, different versions of kernel may detect
different memory ranges, so, you need to compare the output
of /proc/iomem, or BIOS provided RAM map (in dmesg), on different
version kernels, to know why that happened.