Re: ksoftirqd/n permanently eating 60% of a CPU

[Andreas Mohr]

Hi,

Since there hasn't been a reply in a week, let me try to provide at
least a semi-useless one ;)

Such high use probably means that something in the kernel keeps retriggering some
tasklet(?) since it thinks that something hasn't been done yet
(i.e., the tasklet that got triggered didn't manage to satisfy the success
criteria of its owner),
or it means that something "legitimately" uses obscene amounts of
softirqd activity (perhaps some debug infrastructure such as memory tracing
or logging or some such).

Thus:
1. boot with "single" or "init=/bin/bash" kernel commandline and check
   whether the activity still happens
2. if not: boot normally, then remove kernel modules via rmmod one at a
   time, and try shutting down various daemons, to try to find out which
component exactly messes it up

And perhaps running powertop would provide some clues as to the origin
of this CPU hog, despite being a wakeup-specific tracer.

HTH,

Andreas Mohr
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/