All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Carl Jones <carl.jones@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: 2.6.27-rc1 >4096MB issue
Date: Thu, 31 Jul 2008 22:13:41 -0700	[thread overview]
Message-ID: <48929B85.9030004@goop.org> (raw)
In-Reply-To: <df5598920807312025l3a5d9664w2773a133b811ddb4@mail.gmail.com>

Carl Jones wrote:
> Hi,
>
> I'm testing 2.6.27-rc1 and seem to have an issue when booting the domU
> with >4096MB.
>
> Xen: 3.2.1 x86_64 2.6.18.8 xen.org kernel
> domU: 2.6.27-rc1 32bit PAE
>
> # xm list test1
> Name                                        ID   Mem VCPUs      State   Time(s)
> test1                                       24  6000     2     -b----      5.6
> # xm console test1
> free -m
>              total       used       free     shared    buffers     cached
> Mem:          1904         75       1828          0         19         15
> -/+ buffers/cache:         40       1864
> Swap:         2047          0       2047
> testing:~# uname -a
> Linux testing 2.6.27-rc1-xenU #2 SMP Thu Jul 31 22:57:42 EDT 2008 i686 GNU/Linux
>
> (Minimal) Config: http://radium.outervoid.net/~carl/2.6.27-rc1
>
> I see the same when using .26. Am I perhaps missing an option somewhere?
The config has all the obvious things (namely, HIGHMEM64G).

Hm, it does look like something is truncating at 4G and wrapping.  The 
question is whether the system really only has 2G available to it, or if 
it's just mis-reporting.

Can you post the full boot log, and the contents of /proc/meminfo?

Thanks,
    J

  reply	other threads:[~2008-08-01  5:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01  3:25 2.6.27-rc1 >4096MB issue Carl Jones
2008-08-01  5:13 ` Jeremy Fitzhardinge [this message]
2008-08-02  5:22   ` Carl Jones
2008-08-02 16:00     ` Jeremy Fitzhardinge
2008-08-05  1:00       ` Carl Jones
2008-08-05  3:07         ` Jeremy Fitzhardinge
2008-08-05  4:14           ` Carl Jones
2008-08-05  7:09           ` Jan Beulich
2008-08-05 15:52             ` Jeremy Fitzhardinge

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=48929B85.9030004@goop.org \
    --to=jeremy@goop.org \
    --cc=carl.jones@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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.