The patch titled
hpet: avoid warning message livelock
has been removed from the -mm tree. Its filename was
hpet-avoid-warning-message-livelock.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: hpet: avoid warning message livelock
From: Roland Dreier <rdreier@xxxxxxxxx>
I've seen my box paralyzed by an endless spew of
rtc: lost some interrupts at 1024Hz.
messages on the serial console. What seems to be happening is that
something real causes an interrupt to be lost and triggers the
message. But then printing the message to the serial console (from
the hpet interrupt handler) takes more than 1/1024th of a second, and
then some more interrupts are lost, so the message triggers again....
Fix this by adding a printk_ratelimit() before printing the warning.
Signed-off-by: Roland Dreier <rolandd@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
arch/x86_64/kernel/time.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff -puN arch/x86_64/kernel/time.c~hpet-avoid-warning-message-livelock arch/x86_64/kernel/time.c
--- a/arch/x86_64/kernel/time.c~hpet-avoid-warning-message-livelock
+++ a/arch/x86_64/kernel/time.c
@@ -1226,8 +1226,9 @@ static void hpet_rtc_timer_reinit(void)
if (PIE_on)
PIE_count += lost_ints;
- printk(KERN_WARNING "rtc: lost some interrupts at %ldHz.\n",
- hpet_rtc_int_freq);
+ if (printk_ratelimit())
+ printk(KERN_WARNING "rtc: lost some interrupts at %ldHz.\n",
+ hpet_rtc_int_freq);
}
}
_
Patches currently in -mm which might be from rdreier@xxxxxxxxx are
infiniband-work-around-gcc-bug-on-sparc64.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
