From: avi <avi@argo.co.il>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PAE causing failure to run various executables.
Date: Thu, 06 Oct 2005 00:31:51 +0300 [thread overview]
Message-ID: <43444647.4040401@argo.co.il> (raw)
In-Reply-To: <20051005204035.GB10640@redhat.com>
Dave Jones wrote:
>A fedora user recently filed a puzzling bug at
>https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169741
>
>The system being reported has exactly 4GB, and its E820
>tables seem to concur that there is in fact 4GB.
>
>When run in non-PAE mode, it triggers the
>"Warning only 4GB will be used. Use a PAE enabled kernel."
>message, which is odd, but the system does actually run.
>
>
>
if there's a hole in the physical address space (for pci devices), you
would need more than 32 bits to address 4GB RAM.
>When run in PAE mode, it seems to lose its mind, and it
>fails to run various binaries.
>
>Booting with mem=4G causes the machine to boot fine
>(though for some reason, it finds only 3042M of RAM).
>
>
>
looks like a 1GB hole.
>The reporter of this bug has tested on 2.6.14-rc3-git4, and found the
>same issue exists as he saw on the original FC3 kernel, thus ruling out
>any Fedora-specific patches.
>
>Anyone have any ideas what's wrong here?
>
>
>
maybe the last 1GB is bad. since it can only be accessed by pae, only
the pae kernel fails.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2005-10-05 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 20:40 PAE causing failure to run various executables Dave Jones
2005-10-05 21:31 ` avi [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 12:36 Pallipadi, Venkatesh
2005-10-06 13:20 ` Arjan van de Ven
2005-10-06 14:26 ` Avi Kivity
2005-10-06 14:28 ` Arjan van de Ven
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=43444647.4040401@argo.co.il \
--to=avi@argo.co.il \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox