linux-kernel - Re: kdump fails to load and crashes [was: mmotm 2009-11-01-10-01 uploaded]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 03 Nov 2009 16:46:15 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Vivek Goyal <vgoyal@...hat.com>
CC:	linux-kernel@...r.kernel.org, mm-commits@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>, hbabu@...ibm.com,
	kexec@...ts.infradead.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: kdump fails to load and crashes [was: mmotm 2009-11-01-10-01
 uploaded]

On 11/03/2009 04:24 PM, Vivek Goyal wrote:
>> There /proc/iomem looks like:
>> 00100000-12beffff : System RAM
>>   01000000-04ffffff : Crash kernel
>>     01000000-014680c2 : Kernel code
>>     014680c3-016f39f7 : Kernel data
>>     0175b000-017d97ab : Kernel bss
...
> Anyway, can you just try reserving memory at some other address, say
> 64M@32M and see if it works.

Yup, that's it of course. I missed it overlaps with current kernel. I
though they are areas for the crash kernels. Thanks for pointing out. So
the error is we reserve the space for kdump even we can't in fact?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/