#21 Random killing of procceses (allocation failed)

closed
nobody
None
5
2005-02-18
2004-06-03
Anonymous
No

I upgraded to 0.6.1, and kernel randomly kills processes.
h2ocolinux:~# __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0)
VM: killing process apt-cache
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
VM: killing process mysqld
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
VM: killing process dpkg
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
VM: killing process cc1
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
VM: killing process cc1

My CFG file:
<?xml version="1.0" encoding="UTF-8"?>
<colinux>
<!-- This line needs to point to your root file
system.
For example change "root_fs" to the name of the
Debian image.
Inside coLinux it will be /dev/cobd0 -->
<block_device index="0"
path="\DosDevices\g:\coLinux\root_fs"
enabled="true" />

<!-- This line can specify a swap file if you wish,
or an additional
image file, it will /dev/cobd1. Additional
block_devices can
be specified in the same manner by increasing the
index -->

<block_device index="1"
path="\DosDevices\g:\coLinux\swap_device"
enabled="true" />

<block_device index="2"
path="\DosDevices\g:\coLinux\usr_fs"
enabled="true" />

<!-- bootparams allows you to pass kernel boot
parameters -->
<bootparams>root=/dev/cobd0</bootparams>

<!-- image allows you to specify the kernel to boot -->
<image path="vmlinux" />

<!-- this line allows you to specify the amount of
memory available
to coLinux -->
<memory size="64" />

<!-- This allows you to modify networking
parameters, see the README
or website for more information -->
<network index="0" type="bridged" name="Realtek
8139-series PCI NIC" />
</colinux>

Art&#363;ras Šlajus
x11@h2o.pieva.net

Discussion

  • George P Boutwell

    Logged In: YES
    user_id=30412

    Arturas,

    What's the output of free show, especially for the value of
    memory?

    1) Either your don't have swap enabled

    2) You have swap enabled, but you have run linux out of
    memory (including swap), so increase memory &/or swap sizes.

    3) You have a bug, can you try to submit more info on how to
    reproduce it?

    George

     
  • George P Boutwell

    Logged In: YES
    user_id=30412

    Closing this bug as it's not had sufficient activity. Try
    the recent 0.6.2 release and see if it fixes the problem,
    make sure the free program shows swap existing inside
    coLinux guest.

     
  • George P Boutwell

    • status: open --> closed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks