Messages in this thread | | | Date | Sun, 27 Jun 2004 19:30:39 -0700 (PDT) | From | Brian <> | Subject | Kernel VM bug? |
| |
Hello list,
While doing massive memory allocation (I'm using GRASS to project NASA's BlueMarble maps) the kernel apparently tries to kill grass but fails. When I try to access /proc/<grass_pid>/stat the process hangs.
For example, an 'strace' of 'ps' ends like this: open("/proc/1783/stat", O_RDONLY) = 6 read(6, <PS and strace hang here>
I am able to project a few files, but once the filesystem cache fills up, GRASS hangs or gives a panic in vm_stat:381. The strange thing is, very little swap space is in use, and the filesystem cache continues to use most of the RAM.
Is this a kernel bug, or do I need to use kernel 2.6.x (I am using kernel 2.4.26) and /proc/sys/vm/overcommit_memory or similar hack?
Since I am a kernel-newbie, these links might help explain the problem better ;) http://seclists.org/linux-kernel/2001/Dec/1604.html http://www.mail-archive.com/debian-glibc@lists.debian.org/msg10070.html
Brian G
__________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |