Jan Kasprzak <[email protected]> wrote:
>
> Andrew Morton wrote:
> : Jan Kasprzak <[email protected]> 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?
Try `dmesg -n 7' first.
> # dmesg -c >/dev/null; echo -n p >/proc/sysrq-trigger ; sleep 5; dmesg
> SysRq : Show Regs
> #
You won't get anything useful from sysrq-p via /proc/sysrq-trigger - it'll
just show the backtrace of the process `echo'. It has to be via the
keyboard.
If there's no keyboard, do `echo t > /proc/sysrq-trigger' to get an
all-task backtrace, then locate the trace for kswapd in the resulting
output.
Thanks.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
