Commit:     3e94fb8f54c5305ed472e0867cd67d53e05bfb64
Parent:     ee4eff6ff6cbfc8ce38131058a18802bf6206879
Author:     Roland Dreier <[EMAIL PROTECTED]>
AuthorDate: Tue Feb 13 13:26:25 2007 +0100
Committer:  Andi Kleen <[EMAIL PROTECTED]>
CommitDate: Tue Feb 13 13:26:25 2007 +0100

    [PATCH] x86-64: avoid warning message livelock
    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 <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
 arch/x86_64/kernel/time.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/arch/x86_64/kernel/time.c b/arch/x86_64/kernel/time.c
index 9c7fba3..3cc6886 100644
--- a/arch/x86_64/kernel/time.c
+++ b/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 
+                              hpet_rtc_int_freq);
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to