On Mon, 26 Jun 2000, Rik van Riel wrote:
>Usually some vmstat output and a description of what's
>happening from the person experiencing the bug is enough.
Where is this vmstat trace?
>Also, mmap002 on low memory machines seems to be a nice
>way of causing the same thing (program gets killed even
How can you be sure it's even remotely related if you don't have any
vmstat trace? Also vmstat isn't carrying too much information, it's only
the minimum to be able to debug/guess something.
Just think the ramdisk-oom issue fixed in protected-balance patch, that
was _completly_ unrelated with mmap002 even if it was obviously happening
during dirty-cache pressure too.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jun 26 2000 - 21:00:09 EST