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: <4B90D848.5090801@gmail.com>
Date:	Fri, 05 Mar 2010 11:09:12 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	mm-commits@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	the arch/x86 maintainers <x86@...nel.org>,
	Johannes Weiner <hannes@...xchg.org>
Subject: Re: no boot with NO_BOOTMEM=y [was: mmotm 2010-03-02-18-38 uploaded]

On 03/05/2010 01:29 AM, Yinghai Lu wrote:
> On 03/04/2010 07:05 AM, Jiri Slaby wrote:
>> Subject fixed.
>>
>> On 03/04/2010 03:54 PM, Jiri Slaby wrote:
>>> On 03/03/2010 03:39 AM, akpm@...ux-foundation.org wrote:
>>>> The mm-of-the-moment snapshot 2010-03-02-18-38 has been uploaded to
>>>
>>> Hi, the kernel does not boot in qemu-kvm with NO_BOOTMEM=y. The last
>>> message is 'Booting the kernel.'
>>
> 
> tried with kvm/qemu with 512m and 8192m all works here...

Just for the record, I've just found out (thanks to 'mmotm boot panic
bootmem-avoid-dma32-zone-by-default.patch' thread), that when I revert
the patch, NO_BOOTMEM works...

-- 
js
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ