Messages in this thread | | | Date | Wed, 23 Nov 2005 21:24:38 +0100 | From | Jan Kasprzak <> | Subject | Re: 2.6.14 kswapd eating too much CPU |
| |
Andrew Morton wrote: : Jan Kasprzak <kas@fi.muni.cz> wrote: : > : > I am at 2.6.15-rc2 now, the problem is still there. : > Currently according to top(1), kswapd1 eats >98% CPU for 50 minutes now : > and counting. : : When it's doing this, could you do sysrq-p a few times? The output of that : should tell us where the CPU is executing.
Hmm, it does not show anything but the header. Should I enable something special in the kernel?
# dmesg -c >/dev/null; echo -n p >/proc/sysrq-trigger ; sleep 5; dmesg SysRq : Show Regs #
-Yenya
-- | Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> | | GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E | | http://www.fi.muni.cz/~kas/ Journal: http://www.fi.muni.cz/~kas/blog/ | > Specs are a basis for _talking_about_ things. But they are _not_ a basis < > for implementing software. --Linus Torvalds < - 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/
| |