On Sun, 5 Aug 2007 19:03:12 +0300 Dimitrios Apostolou <[EMAIL PROTECTED]> wrote:
> was my report so complicated? We're bad. Seems that your context switch rate when running two instances of badblocks against two different disks went batshit insane. It doesn't happen here. Please capture the `vmstat 1' output while running the problematic workload. The oom-killing could have been unrelated to the CPU load problem. iirc badblocks uses a lot of memory, so it might have been genuine. Keep an eye on the /proc/meminfo output and send the kernel dmesg output from the oom-killing event. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
