linux-kernel - Re: 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-prev] [day] [month] [year] [list]

Message-ID: <20100408041416.GB3978@cr0.nay.redhat.com>
Date:	Thu, 8 Apr 2010 12:14:16 +0800
From:	Amerigo Wang <xiyou.wangcong@...il.com>
To:	Ryan Wang <openspace.wang@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: BUG? boot failed with "crashkernel=256M@32M", but
 "crashkernel=256M@64M" can work

On Thu, Apr 08, 2010 at 11:58:17AM +0800, Ryan Wang wrote:
>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?

It could be.

What failure did you meet? And your boot log?

Also, which version are you using?

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/