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

Message-ID: <20100319131208.GA3911@dhcp-lab-161.englab.brq.redhat.com>
Date:	Fri, 19 Mar 2010 14:12:09 +0100
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	linux-kernel@...r.kernel.org
Cc:	Yinghai Lu <yinghai@...nel.org>, "H. Peter Anvin" <hpa@...or.com>
Subject: Can not boot with CONFIG_NO_BOOTMEM=y on i686

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.

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