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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <21d7e9971003221844k6ce67f40k69981ff92f29f20b@mail.gmail.com>
Date:	Tue, 23 Mar 2010 11:44:53 +1000
From:	Dave Airlie <airlied@...il.com>
To:	Stanislaw Gruszka <sgruszka@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, Yinghai Lu <yinghai@...nel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: Can not boot with CONFIG_NO_BOOTMEM=y on i686

On Fri, Mar 19, 2010 at 11:12 PM, Stanislaw Gruszka <sgruszka@...hat.com> wrote:
> Hello.
>
> After update to 2.6.34-rc1, I was experimented by strange oopses during
> boot, what looked like memory corruption. Bisection shows that first bad
> commit is 59be5a8e8ce765cf739ec7f07176219972de7481 ("x86: Make 32bit
> support NO_BOOTMEM"). When I disable CONFIG_NO_BOOTMEM I'm able to start
> system. Not sure what info is need to track down this issue, so please
> let me know.
>

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.

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