WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[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: Tue, 14 Feb 2006 19:49:54 +0000
Delivery-date: Tue, 14 Feb 2006 20:13:09 +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
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=522





------- Additional Comments From dbarrera@xxxxxxxxxx  2006-02-14 19:49 -------
(In reply to comment #8)
> This seems normal behavior, 
Agree that OOM should kill offending tasks. If it is normal behavior, then I
should close the defect, but I want to be sure that it is not a problem.
> 
> How many memory do you have in domains that goes out-of-memory (seems it is 
> 256M
> but I'm not sure) ?
Yes, 256MB
> Is that a new behavior ? if yes, since when ?
OOM killing lmbench is not new behavior. However, I had not seen the traces
before. Seems like they started showing up after changeset 8758 (not sure 
though).
> 
> BTW, you forget to label which trace correspond to dom0 and domU (with there
> respective configs would be even better)
You are absolutely right.


Here's one from domU today,using changeset 8830.
oom-killer: gfp_mask=0x201d2, order=0

Call Trace: <ffffffff8012e5ec>{printk_ratelimit+21}
       <ffffffff80156506>{out_of_memory+55} 
<ffffffff80158661>{__alloc_pages+555}
       <ffffffff80159e05>{__do_page_cache_readahead+267}
<ffffffff8031a0d3>{__wait_on_bit_lock+103}
       <ffffffff80152d88>{sync_page+0}
<ffffffff8015a0d8>{do_page_cache_readahead+81}
       <ffffffff80154d1f>{filemap_nopage+325}
<ffffffff8016373a>{__handle_mm_fault+1494}
       <ffffffff80188f03>{poll_freewait+87} 
<ffffffff801192c5>{do_page_fault+1989}
       <ffffffff80255eeb>{copy_user_generic+22} 
<ffffffff80189c31>{sys_select+935}
       <ffffffff8010e7d7>{error_exit+0}
Mem-info:
DMA per-cpu:
cpu 0 hot: high 186, batch 31 used:31
cpu 0 cold: high 62, batch 15 used:58
DMA32 per-cpu: empty
Normal per-cpu: empty
HighMem per-cpu: empty
Free pages:        2924kB (0kB HighMem)
Active:60890 inactive:60791 dirty:0 writeback:0 unstable:0 free:731 slab:2381
mapped:121670 pagetables:1091
DMA free:2924kB min:2916kB low:3644kB high:4372kB active:243560kB
inactive:243164kB present:532480kB pages_scanned:164357 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB
pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB
pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
HighMem free:0kB min:128kB low:128kB high:128kB active:0kB inactive:0kB
present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0 0
DMA: 15*4kB 4*8kB 3*16kB 1*32kB 1*64kB 1*128kB 0*256kB 1*512kB 0*1024kB 1*2048kB
0*4096kB = 2924kB
DMA32: empty
Normal: empty
HighMem: empty
Swap cache: add 377075, delete 377075, find 299/391, race 0+0
Free swap  = 0kB
Total swap = 1052216kB
Free swap:            0kB
133120 pages of RAM
5721 reserved pages
13 pages shared
0 pages swap cached
Out of Memory: Killed process 10230 (mem01).



-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs