This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 522] oom-killer: gfp_mask=0x201d2, order=

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 522] oom-killer: gfp_mask=0x201d2, order=
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 13 Feb 2006 14:58:57 +0000
Delivery-date: Mon, 13 Feb 2006 15:21:42 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From vincent.hanquez@xxxxxxxxxxxx  2006-02-13 14:58 
This seems normal behavior, when running out of memory & swap, the kernel start
killing task. now the attached files contains lots of different errors, lots of
them seem not related to the specific problem.

This is very weird since this occurs in filemap_nopage (make sense lmbench does
lots of mmap), which is supposed to give only cache page .. memory that can be
easily reclaim.

How many memory do you have in domains that goes out-of-memory (seems it is 256M
but I'm not sure) ?
Is that a new behavior ? if yes, since when ?

BTW, you forget to label which trace correspond to dom0 and domU (with there
respective configs would be even better)

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list