From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Nathan March <nathan@gt.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: SLUB allocation error on 3.0.3 / 4.1.1
Date: Mon, 12 Sep 2011 16:17:40 -0400 [thread overview]
Message-ID: <20110912201740.GB11900@oracle.com> (raw)
In-Reply-To: <4E6E62E8.4050400@gt.net>
> total_memory : 98294
> free_memory : 36580
> free_cpus : 0
> xen_major : 4
> xen_minor : 1
> xen_extra : .1
> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p
> hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler : credit
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset : unavailable
> xen_commandline : console=com1,com2,vga com1=115200,8n1
> com2=115200,8n1 dom0_mem=1024M dom0_max_vcpus=1 dom0_vcpus_pin=true
> cc_compiler : gcc version 4.3.4 (Gentoo 4.3.4 p1.1, pie-10.1.5)
> cc_compile_by : root
> cc_compile_domain : nmsrv.com
> cc_compile_date : Mon Aug 22 11:28:50 PDT 2011
> xend_config_format : 4
>
> Seeing this on multiple dom0's which are all running identical
> hardware (Supermicro X8DTT w/ Intel 82574L gige). Dom0's are limited
> to 1gb (dom0_mem=1024M dom0_max_vcpus=1 dom0_vcpus_pin=true)
> although they don't go above 250mb used.
>
> Not sure if this is a xen bug, network driver issue or something else?
It is a Linux kernel bug. It does not respect the dom0_mem=max:X argument
so you end up with 98GB of pagetables in Dom0 and you can't allocate
enough memory for your normal drivers (since most of the memory is used
for your non-used pagetables).
The workaround is to put in your Linux command-line: "mem=1GB"
(and keep the dom0_mem=..) arguments.
A patch in 3.0.4 (or 3.0.5) should soon surface which will fix this.
prev parent reply other threads:[~2011-09-12 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 19:52 SLUB allocation error on 3.0.3 / 4.1.1 Nathan March
2011-09-12 20:17 ` Konrad Rzeszutek Wilk [this message]
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=20110912201740.GB11900@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=nathan@gt.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).