linux-kernel - BUG? boot failed with "crashkernel=256M@32M", but "crashkernel=256M@64M" can work

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-next>] [day] [month] [year] [list]

Message-ID: <h2k5d592f661004072058hcdac7ab5y3eceeaab28f6fbe0@mail.gmail.com>
Date:	Thu, 8 Apr 2010 11:58:17 +0800
From:	Ryan Wang <openspace.wang@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: BUG? boot failed with "crashkernel=256M@32M", but 
	"crashkernel=256M@64M" can work

Hi all,

        I have setup kdump on my box, but failed on booting with
                       "crashkernel=256M@32M".
Then I tried
                       "crashkernel=256M@64M"
and succeeded.

       Is it a bug of kernel?

thanks,
--
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/