On Fri, Mar 19, 2010 at 11:12 PM, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
quoted text
> 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.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/