[lkml]   [2007]   [Feb]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[PATCH x86 for review III] [8/29] x86_64: avoid warning message livelock

    From: Roland Dreier <>

    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 <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Andi Kleen <>

    arch/x86_64/kernel/time.c | 5 +++--
    1 file changed, 3 insertions(+), 2 deletions(-)
    Index: linux/arch/x86_64/kernel/time.c
    --- linux.orig/arch/x86_64/kernel/time.c
    +++ linux/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);

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at
     \ /
      Last update: 2007-02-12 17:55    [from the cache]
    ©2003-2014 Jasper Spaans. hosted at Digital Ocean