Displaying 4 results from an estimated 4 matches for "swap_map".
2007 Aug 21
2
[PATCH] Fix lazy mode vmalloc synchronization for paravirt
Found this looping Ubuntu installs with VMI.
If unlucky enough to hit a vmalloc sync fault during a lazy mode =
operation (from an IRQ handler for a module which was not yet populated =
in current page directory, or from inside copy_one_pte, which touches =
swap_map, and hit in an unused 4M region), the required PDE update would =
never get flushed, causing an infinite page fault loop.
This bug affects any paravirt-ops backend which uses lazy updates, I =
believe that makes it a bug in Xen, VMI and lguest. It only happens on =
LOWMEM kernels.
Currently f...
2007 Aug 21
2
[PATCH] Fix lazy mode vmalloc synchronization for paravirt
Found this looping Ubuntu installs with VMI.
If unlucky enough to hit a vmalloc sync fault during a lazy mode =
operation (from an IRQ handler for a module which was not yet populated =
in current page directory, or from inside copy_one_pte, which touches =
swap_map, and hit in an unused 4M region), the required PDE update would =
never get flushed, causing an infinite page fault loop.
This bug affects any paravirt-ops backend which uses lazy updates, I =
believe that makes it a bug in Xen, VMI and lguest. It only happens on =
LOWMEM kernels.
Currently f...
2008 Jul 16
7
Please help: domU becomes unresponsive
...50% of TOTAL MEM
SLAB 358565 1.4 GB 13% of TOTAL MEM
TOTAL HIGH 0 0 0% of TOTAL MEM
FREE HIGH 0 0 0% of TOTAL HIGH
TOTAL LOW 2621696 10 GB 100% of TOTAL MEM
FREE LOW 8884 34.7 MB 0% of TOTAL LOW
kmem: swap_info[0].swap_map at ffffff00001ea000 is unaccessible
So I see where the DomU is, but how did it get there? Can I find out
from crash, or do I need something "real-time" within the DomU? Of
course, searching has given me nothing to go on, hence this post, but
I''ll continue...
Tia,
jerry
--
&qu...
2008 Jul 14
2
Need kernel-debuginfo-2.6.9-67.0.20.EL.x86_64.rpm
Short story:
Would it be possible to get
kernel-debuginfo-2.6.9-67.0.20.EL.x86_64.rpm on di.c.o?
I have a need to run crash on a 2.6.9-67.0.20.ELxenU xm dump-core.
Long story:
Two Dell 6950 (now called R905, 4 Dual-Core AMD Opteron 8200 series)
heartbeat/drbd nodes running the stock CentOS 5.2 Dom0. The domU's are
the only resources in heartbeat.
Dom1 is a perfectly running, updated, CentOS