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: <4BA98FA8.1040600@kernel.org>
Date:	Tue, 23 Mar 2010 21:06:00 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Stanislaw Gruszka <sgruszka@...hat.com>
CC:	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	Dave Airlie <airlied@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Tejun Heo <tj@...nel.org>
Subject: Re: Can not boot with CONFIG_NO_BOOTMEM=y on i686

On 03/23/2010 04:35 AM, Stanislaw Gruszka wrote:
> On Sat, Mar 20, 2010 at 11:26:06AM -0700, Yinghai Lu wrote:
>>> 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.
>>
>> can you check patch
>>
>> https://patchwork.kernel.org/patch/87081/
> 
> Patch helps somehow. Instead of many random oopses, now I have one and
> the same oops, here is photo:
> http://people.redhat.com/sgruszka/20100322_001.jpg

how does e820 look like?

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