RE: spurious 8259A interrupt

From: Guennadi Liakhovetski (g.liakhovetski_at_gmx.de)
Date: 03/22/04

  • Next message: Jeff Garzik: "Re: 2.6.0 lockup with de4x5/de2104x driver"
    Date:	Mon, 22 Mar 2004 22:16:01 +0100 (CET)
    To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
    
    

    On Mon, 22 Mar 2004, Maciej W. Rozycki wrote:

    > Do you really get "spurious 8259A interrupt" messages for the local APIC
    > timer??? They don't ever leave the unit bound to the processor -- it has
    > to be something else. What is your contents of /proc/interrupts?

    Ok, here's exactly, what I see:
    1) during start-up 1 message
    spurious 8259A interrupt: IRQ7.
    2) at run-time ERR: count increases - sometimes several per
    second, sometimes it remains constant for some time.
    3) No more "spurious" messages
    4) I saw definitely situations, when between 2 /proc/interrupts snapshots
    the sum of all (except the timer) interrupts was smaller, than the number
    of errors, e.g.

               CPU0 (2nd shot)
      0: 36557 37638 +1081 XT-PIC timer
      1: 59 65 +6 XT-PIC i8042
      2: 0 0 XT-PIC cascade
      5: 0 0 XT-PIC VIA686A
      8: 3 3 XT-PIC rtc
      9: 0 0 XT-PIC acpi, uhci_hcd, uhci_hcd
     10: 0 0 XT-PIC eth0
     12: 84 84 XT-PIC i8042
     14: 1910 1918 +8 XT-PIC ide0
     15: 1 1 XT-PIC ide1
    NMI: 18 18
    LOC: 36460 37541 +1081
    ERR: 36 57 +21

    ide0 + i8042 (keyboard) = 14, whereas errors increased by 21. So, if you
    are right, than Alan's wrong (or my understanding of his statement), and
    those spurious interrupts occur not only after real ones, or, one real
    interrupt can produce several spurious ones.

    Thanks
    Guennadi

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

  • Next message: Jeff Garzik: "Re: 2.6.0 lockup with de4x5/de2104x driver"

    Relevant Pages

    • Re: [PATCH] 3c59x: read current link status from phy
      ... there is only one interrupt that for data transmission (both Tx ... The MII registers are not ... Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: is killing zombies possible w/o a reboot?
      ... An interrupt could be received at any time, ... in uninterruptible state because it is uninterruptible ... Processes must never get stuck in D, it's a kernel bug. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.0-test7-mm1
      ... >> handlers happens to start a thread, ... Problem is, things like bus resets happen in interrupt, and while I can ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: CONFIG_IRQBALANCE for AMD64?
      ... Provide some sort of cache-affinity for network interrupt processing, ... Utilize idle CPUs where possible to shoulder the load. ... I'll confess to not having looked at non-i386 arches. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.10-ck4
      ... Kernel panic - not syncing: Fatal exception in interrupt. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)