Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct

From: Randy.Dunlap (rddunlap_at_osdl.org)
Date: 08/11/03

  • Next message: Robert Love: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"
    Date:	Sun, 10 Aug 2003 20:48:47 -0700 (PDT)
    To: <cmrivera@ufl.edu>
    
    

    > Hi,
    >
    > I am running 2.6.0-test2-mm4 on an SMP machine with dual Athlon MP 2000+s.
    >
    > /proc/stat displays:
    >
    > cpu 13261 0 2603 887671 4399
    > cpu0 6936 0 1571 443183 2285
    > cpu1 6325 0 1031 444488 2113
    > intr 5021986 4539589 5476 0 0 0 0 0 0 0 0 0 0 73888 0 16345 11 379144 0 7533
    > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    > ctxt 1677244
    > btime 1060567182
    > processes 1286
    > procs_running 1
    > procs_blocked 0
    >
    > /proc/interrupts:
    >
    > CPU0 CPU1
    > 0: 26530 4875571 IO-APIC-edge timer
    > 1: 6035 0 IO-APIC-edge i8042
    > 2: 0 0 XT-PIC cascade
    > 12: 77657 3869 IO-APIC-edge i8042
    > 14: 16560 1 IO-APIC-edge ide0
    > 15: 11 0 IO-APIC-edge ide1
    > 16: 409959 1 IO-APIC-level radeon@PCI:1:5:0
    > 17: 0 0 IO-APIC-level EMU10K1
    > 18: 7942 0 IO-APIC-level eth0
    > NMI: 0 0
    > LOC: 4902124 4902123
    > ERR: 0
    > MIS: 0
    >
    > I am not sure why the intr line contains all those zeros. Is this normal
    > behavior?

    Yes, for most architectures, it prints interrupts from 0 thru NR_IRQS:
            for (i = 0 ; i < NR_IRQS ; i++)
                    len += sprintf(page + len, " %u", kstat_irqs(i));
    and NR_IRQS varies depending on the kernel build options, but (for x86)
    is usually either 16 or 224.

    ~Randy

    -
    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: Robert Love: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"

    Relevant Pages

    • Re: 2.4.x kernel uptime counter problem
      ... Does require no reboot and should work ... /proc/stat (btime), and it isn't that hard to turn it into whatever format you ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: 2.6.1: process start times by procps
      ... I would like to make my bug report more accurate: ... (The relative error is the same: ... so this is probably not correct, but at least btime seemed to stay constant. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.1: process start times by procps
      ... > ps output after uptime of a couple of weeks.) ... > so this is probably not correct, but at least btime seemed to stay constant. ... > guess ps can't possibly get its calculations involving HZ right. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.1: process start times by procps
      ... Hmm. ... >> Thus if your time of day is adjusted by NTP, btime will change as well. ... My patch changed btime to be ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.6 breaks kmail (nfs related?)
      ... On Sun, 16 May 2004, Trond Myklebust wrote: ... They were in the original email on the kernel mailing list: ... The only thing there is that "intr". ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)