From: Michal Hocko <mhocko@suse.cz>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86-32 PAE-enabled kernel fails to boot with 64GB of RAM
Date: Tue, 6 Dec 2011 11:26:28 +0100 [thread overview]
Message-ID: <20111206102628.GC1342@tiehlicka.suse.cz> (raw)
In-Reply-To: <CACqU3MXMAP-7LtVWHENNAQSS+B0c5qVcdWq=4NFGNACxkTRYzg@mail.gmail.com>
On Tue 06-12-11 02:23:26, Arnaud Lacombe wrote:
> Hi,
Hi,
>
> I've been playing a bit with PAE and 3.2-rc3 this evening and found
> out to be unable to use the full 64GB address space.
Quoting from Documentation/vm/highmem.txt:
"
The general recommendation is that you don't use more than 8GiB on a
32-bit machine - although more might work for you and your workload,
you're pretty much on your own - don't expect kernel developers to
really care much if things come apart.
"
> More precisely,
> the attached config, fails to detect the disk correctly:
>
> excerpt from `dmesg.64GB.txt' (bad):
>
> scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 0.14 PQ: 0 ANSI: 5
> sd 0:0:0:0: [sda] 107856 512-byte logical blocks: (55.2 MB/52.6 MiB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't
> support DPO or FUA
> sda: unknown partition table
> sd 0:0:0:0: Attached scsi generic sg0 type 0
>
> excerpt from `dmesg.16GB.txt' (good):
>
> scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 0.14 PQ: 0 ANSI: 5
> sd 0:0:0:0: [sda] 107856 512-byte logical blocks: (55.2 MB/52.6 MiB)
> sd 0:0:0:0: Attached scsi generic sg0 type 0
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't
> support DPO or FUA
> sda: sda1 sda2
>
> The theoretical use-case I would think about is a machine running an
> x86-64 kernel with +64GB of RAM, but used to boot an x86-32 kernel
> every once in a while to do some work. I would naively expect such a
> PAE-enabled kernel to be limited to 64GB of RAM, but still be
> functional.
There are many issues with PAE. You still have a big pressure on the
lowmem (turning different CONFIG_*DEBUG like the one for SLUB doesn't
help...).
[...]
> ps: instability starts to appear consistently above 65000MB of RAM, at
> 65025MB, the kernel BUG() on the following:
>
> PCI: Using ACPI for IRQ routing^M
> PCI: pci_cache_line_size set to 32 bytes^M
> reserve RAM buffer: 000000000009f400 - 000000000009ffff ^M
> reserve RAM buffer: 00000000dfffd000 - 00000000dfffffff ^M
> reserve RAM buffer: 0000001000100000 - 0000001003ffffff ^M
> BUG: unable to handle kernel paging request at 1f90c2f2^M
> IP: [<c1003cbf>] print_context_stack+0x6e/0x8d^M
> *pdpt = 0000000000000000 *pde = 0000000000000000 ^M
> Thread overran stack, or stack corrupted^M
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You overrun your stack...
[...]
--
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9
Czech Republic
next prev parent reply other threads:[~2011-12-06 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 7:23 Arnaud Lacombe
2011-12-06 10:26 ` Michal Hocko [this message]
2011-12-06 18:13 ` H. Peter Anvin
2011-12-21 6:34 ` Yuhong Bao
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=20111206102628.GC1342@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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
Powered by JetHome