From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"kernel list" <linux-kernel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Suspected regression in "x86: extend e820 ealy_res support 32bit"
Date: Wed, 21 May 2008 18:43:59 -0700 [thread overview]
Message-ID: <86802c440805211843m51a9b56bjd28a01d008541e9a@mail.gmail.com> (raw)
In-Reply-To: <4834AF0C.2000601@goop.org>
On Wed, May 21, 2008 at 4:23 PM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Yinghai Lu wrote:
>>
>> noticed that bootmap_size is shifted already...
>>
>> please use attached patch to see if bootmap is right...
>>
>
> Unfortunately its a bit difficult because printk() output isn't appearing at
> early boot (not sure why). I'll try to extract something useful tomorrow.
>
> Perhaps this is helpful:
>
> This the e820 map of a regular boot:
>
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 000000000009f000 (usable)
> Xen: 0000000000100000 - 0000000010000000 (usable)
> debug: ignoring loglevel setting.
> limit_regions start: 0000000000000000 - 000000000009f000 (usable)
> limit_regions start: 0000000000100000 - 0000000010000000 (usable)
> limit_regions endfunc: 0000000000000000 - 000000000009f000 (usable)
> limit_regions endfunc: 0000000000100000 - 0000000010000000 (usable)
> user-defined physical RAM map:
> user: 0000000000000000 - 000000000009f000 (usable)
> user: 0000000000100000 - 0000000010000000 (usable)
> 0MB HIGHMEM available.
> 256MB LOWMEM available.
> [...]
> Entering add_active_range(0, 0, 65536) 0 entries of 256 used
> Zone PFN ranges:
> DMA 0 -> 4096
> Normal 4096 -> 65536
> HighMem 65536 -> 65536
> Movable zone start PFN for each node
> early_node_map[1] active PFN ranges
> 0: 0 -> 65536
> On node 0 totalpages: 65536
> DMA zone: 56 pages used for memmap
> DMA zone: 0 pages reserved
> DMA zone: 4040 pages, LIFO batch:0
> Normal zone: 840 pages used for memmap
> Normal zone: 60600 pages, LIFO batch:15
> HighMem zone: 0 pages used for memmap
> Movable zone: 0 pages used for memmap
>
>
please check patch
http://lkml.org/lkml/2008/5/21/570
[PATCH] x86: extend e820 ealy_res support 32bit - fix
also please try to boot with
console=uart8250,io,0x3f8,115200n8
to get more early printout...
YH
next prev parent reply other threads:[~2008-05-22 1:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <483467CD.90401@goop.org>
2008-05-21 20:35 ` Yinghai Lu
2008-05-21 22:01 ` Jeremy Fitzhardinge
2008-05-21 22:40 ` Yinghai Lu
2008-05-21 23:23 ` Jeremy Fitzhardinge
2008-05-22 1:43 ` Yinghai Lu [this message]
2008-05-21 23:14 ` Johannes Weiner
2008-05-21 23:23 ` Yinghai Lu
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=86802c440805211843m51a9b56bjd28a01d008541e9a@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®