From: Yinghai Lu <yinghai@kernel.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Dave Airlie <airlied@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: Can not boot with CONFIG_NO_BOOTMEM=y on i686
Date: Tue, 23 Mar 2010 21:06:00 -0700 [thread overview]
Message-ID: <4BA98FA8.1040600@kernel.org> (raw)
In-Reply-To: <20100323113551.GA3862@dhcp-lab-161.englab.brq.redhat.com>
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
next prev parent reply other threads:[~2010-03-24 4:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 13:12 Can not boot with CONFIG_NO_BOOTMEM=y on i686 Stanislaw Gruszka
2010-03-20 18:26 ` Yinghai Lu
2010-03-23 11:35 ` Stanislaw Gruszka
2010-03-24 4:06 ` Yinghai Lu [this message]
2010-03-24 9:04 ` Stanislaw Gruszka
2010-03-26 8:10 ` Yinghai Lu
2010-03-26 12:10 ` Stanislaw Gruszka
2010-03-26 12:45 ` Johannes Weiner
2010-03-26 18:18 ` Yinghai Lu
2010-03-23 1:44 ` Dave Airlie
2010-03-29 21:05 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BA98FA8.1040600@kernel.org \
--to=yinghai@kernel.org \
--cc=airlied@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sgruszka@redhat.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.