The patch titled NOHZ: Rate limit the local softirq pending warning output has been added to the -mm tree. Its filename is nohz-rate-limit-the-local-softirq-pending-warning-output.patch *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: NOHZ: Rate limit the local softirq pending warning output From: Thomas Gleixner <tglx@xxxxxxxxxxxxx> The warning in the NOHZ code, which triggers when a CPU goes idle with softirqs pending can fill up the logs quite quickly. Rate limit the output until we found the root cause of that problem. Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx> Cc: <stable@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- kernel/time/tick-sched.c | 12 +++++++++--- 1 files changed, 9 insertions(+), 3 deletions(-) diff -puN kernel/time/tick-sched.c~nohz-rate-limit-the-local-softirq-pending-warning-output kernel/time/tick-sched.c --- a/kernel/time/tick-sched.c~nohz-rate-limit-the-local-softirq-pending-warning-output +++ a/kernel/time/tick-sched.c @@ -167,9 +167,15 @@ void tick_nohz_stop_sched_tick(void) goto end; cpu = smp_processor_id(); - if (unlikely(local_softirq_pending())) - printk(KERN_ERR "NOHZ: local_softirq_pending %02x\n", - local_softirq_pending()); + if (unlikely(local_softirq_pending())) { + static int ratelimit; + + if (ratelimit < 10) { + printk(KERN_ERR "NOHZ: local_softirq_pending %02x\n", + local_softirq_pending()); + ratelimit++; + } + } now = ktime_get(); /* _ Patches currently in -mm which might be from tglx@xxxxxxxxxxxxx are ignore-bogus-acpi-info-for-offline-cpus.patch nohz-rate-limit-the-local-softirq-pending-warning-output.patch drm-spinlock-initializer-cleanup.patch s390-spinlock-initializer-cleanup.patch i386-hpet-check-if-the-counter-works.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html