==resending comment to the list== On 3/27/07, Judith Lebzelter <[EMAIL PROTECTED]> wrote: > On Tue, Mar 27, 2007 at 10:45:38AM +0530, Vivek Goyal wrote: > > On Mon, Mar 26, 2007 at 04:47:29PM -0700, Judith Lebzelter wrote: > > > > Hi > > > > > > > > Looks like reserving memory([EMAIL PROTECTED]) for crash kernel failed > > > > for some reason. > > > > Debug statements in the first kernel might help. > > > > > > Yes, but I cannot see what is wrong with my configuration. It does seem > > > like it needs some deeper debugging. Could you point me at a file or > > > files > > > to look at? > > > > > > > > > > What does /proc/iomem show > > > > at this memory range? > > > > > > It shows it as part of System RAM, but nothing specific: > > > > > > 00100000-03ff7fff : System RAM > > > > Looking at above line, you seem to be having only 63 or 64 MB RAM in the > > system. Or, somehow rest of the RAM is mapped beyond ACPI tables or > > something like that. Once you paste whole of the /proc/iomem output, only > > then we will come to know. > > Okay here is the whole file: > > 00000000-0009bfff : System RAM > 0009c000-0009ffff : reserved > 000a0000-000bffff : Video RAM area > 000c0000-000c7fff : Video ROM > 000c8000-000c97ff : Adapter ROM > 000cd800-000d27ff : Adapter ROM > 000f0000-000fffff : System ROM > 00100000-03ff7fff : System RAM > 00100000-0039f367 : Kernel code > 0039f368-004ab80b : Kernel data > 03ff8000-03fffbff : ACPI Tables > 03fffc00-03ffffff : ACPI Non-volatile Storage > 04000000-efffffff : System RAM [device io mapped cut for brevity] > fec00000-ffffffff : reserved > 100000000-30fffffff : System RAM > > > > > Well it alteast explains that why crashkernel=X&Y is failing. There is > > not sufficient RAM at that location to reserve. > > > > Thanks > > Vivek > > > > > 00100000-0039f367 : Kernel code > > > 0039f368-004ab80b : Kernel data > > > 03ff8000-03fffbff : ACPI Tables > > >
Judith, To use the crash kernel parameter, CONFIG_CRASH_DUMP must be set. Only then will "kexec -p" work. Without that option the kernel will not reserve the memory on the command line. AFAIK, you don't need to set "CONFIG_PHYSICAL_ALIGN=0x100000" to use KEXEC (kexec -l), but don't hold me to that since I am always running with those parameters set and I haven't checked the code. 12GB looks like enough space for a crash kernel. HTH Amul _______________________________________________ fastboot mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/fastboot
