From: Bill C. R. <do...@fr...> - 2004-05-26 20:08:39
|
I am still using version 0.60. I'm just wondering if any of the more receint versions have solved the coLinux memory problems? They are starting to get annoying... ... Journalled Block Device driver loaded devfs: v1.12c (20020818) Richard Gooch (rg...@at...) devfs: boot_options: 0x0 pty: 256 Unix98 ptys configured RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) cobd0 size: 3618 kb cobd1 size: 4194240 kb cobd2 size: 4194240 kb cobd3 size: 11736 kb cobd4 size: 64 kb cobd: loaded (max 8 devices) NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 4096 bind 8192) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. FAT: bogus logical sector size 0 UMSDOS: msdos_read_super failed, mount aborted. FAT: bogus logical sector size 0 FAT: bogus logical sector size 0 ISO 9660 Extensions: RRIP_1991A VFS: Mounted root (iso9660 filesystem) readonly. Freeing unused kernel memory: IMPLEMENTATION MISSING Adding Swap: 2097136k swap-space (priority -1) daemon: module connected: conet0 co_message_switch: setting callback rule for 8 daemon: module connected: console co_message_switch: setting callback rule for 6 reiserfs: found format "3.6" with standard journal reiserfs: checking transaction log (device cobd(117,2)) ... for (cobd(117,2)) cobd(117,2):Using r5 hash to sort names conet0: initialized __alloc_pages: 0-order allocation failed (gfp=0xf0/0) __alloc_pages: 0-order allocation failed (gfp=0xf0/0) __alloc_pages: 0-order allocation failed (gfp=0xf0/0) __alloc_pages: 0-order allocation failed (gfp=0xf0/0) __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) VM: killing process ld.so |