linux-kernel - Re: Can not boot with CONFIG_NO

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4BB11605.4080405@zytor.com>
Date:	Mon, 29 Mar 2010 14:05:09 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Dave Airlie <airlied@...il.com>
CC:	Stanislaw Gruszka <sgruszka@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Yinghai Lu <yinghai@...nel.org>
Subject: Re: Can not boot with CONFIG_NO_BOOTMEM=y on i686

On 03/22/2010 06:44 PM, Dave Airlie wrote:
> 
> I had a similar issue today, wasted a morning try to get either -rc1
> or -rc2 to boot on my 32-bit desktop here,
> until I worked out that the default for this option is to be on.
> 
> I suggest CONFIG_NO_BOOTMEM be default n for now.
> 
> Not sure why it was merged as default y.
> 

Because it was only a "chicken bit" to allow for debugging in case/when
something broke (which it has, indeed, allowed.)

	-hpa

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