Dodgy hardware, I'm afraid - it looks like a cross-CPU interrupt
was sent but not received. Not uncommon.
> The interesting thing is that i don't have any swap, so i'm really
> interested
> in knowing why kswapd is envolved here.
Look at the swapout code: it calls flush_tlb_page() in preparation
for swapping a page out. It then tries to allocate swap space,
finds there is none and bales out. This can comsume quite a lot
of CPU under some circumstances.
-
-
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/