On Tue, Mar 27, 2007 at 10:09:42AM -0700, Judith Lebzelter 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
This chunk does not have enough space to hold 64MB of memory starting at 16MB. Hence memory reservation is failing. > 03ff8000-03fffbff : ACPI Tables > 03fffc00-03ffffff : ACPI Non-volatile Storage > 04000000-efffffff : System RAM This look big enough..Could you try passing [EMAIL PROTECTED] while booting the first kernel? You will need to build the second kernel for 64MB. Thanks Rachita > f1000000-f10fffff : 0000:00:05.0 > f1100000-f1107fff : 0000:00:0c.0 > f1108000-f110ffff : 0000:02:05.0 > f1120000-f113ffff : 0000:01:05.0 > f1200000-f12fffff : 0000:01:07.0 > f1300000-f13fffff : 0000:01:07.1 > f1400000-f15fffff : 0000:03:05.0 > f8000000-f8001fff : 0000:00:0a.0 > f8000000-f8001fff : sym53c8xx > f8002000-f8003fff : 0000:00:0a.1 > f8002000-f8003fff : sym53c8xx > f8004000-f8004fff : 0000:00:05.0 > f8004000-f8004fff : e100 > f8005000-f8005fff : 0000:00:0c.0 > f8006000-f80060ff : 0000:00:00.0 > f8006400-f80067ff : 0000:00:0a.0 > f8006400-f80067ff : sym53c8xx > f8006800-f8006bff : 0000:00:0a.1 > f8006800-f8006bff : sym53c8xx > f8100000-f81fffff : 0000:00:05.0 > f8100000-f81fffff : e100 > fa000000-fbffffff : 0000:00:0c.0 > fc000000-fc01ffff : 0000:01:07.0 > fc020000-fc03ffff : 0000:01:07.0 > fc040000-fc05ffff : 0000:01:07.1 > fc060000-fc07ffff : 0000:01:07.1 > fc080000-fc080fff : 0000:01:05.0 > fc080000-fc080fff : qla2xxx > fc081000-fc0810ff : 0000:01:00.0 > fc300000-fc300fff : 0000:02:05.0 > fc301000-fc3010ff : 0000:02:00.0 > fc400000-fc5fffff : 0000:02:05.0 > fc800000-fc80ffff : 0000:03:05.0 > fc810000-fc813fff : 0000:03:05.0 > fc814000-fc8140ff : 0000:03:00.0 > 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 > > > _______________________________________________ fastboot mailing list fastboot@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/fastboot
