1. Home
2. Stations
3. ATD-28-7
4. irqstats

Graph information

Shows the number of different IRQs received by the kernel. High disk or network traffic can cause a high number of interrupts (with good hardware and drivers this will be less so). Sudden high interrupt activity with no associated higher system activity is not normal.

Field	Internal name	Type	Warning	Critical	Info
timer [0]	i0	derive			Interrupt 0, for device(s): timer
i8042 [1]	i1	derive			Interrupt 1, for device(s): i8042
pata_rdc [14]	i14	derive			Interrupt 14, for device(s): pata_rdc
pata_rdc [15]	i15	derive			Interrupt 15, for device(s): pata_rdc
cascade [2]	i2	derive			Interrupt 2, for device(s): cascade
XT-PIC-XT [3]	i3	derive			Interrupt 3, for device(s): XT-PIC-XT
serial [4]	i4	derive			Interrupt 4, for device(s): serial
ohci_hcd:usb2 [5]	i5	derive			Interrupt 5, for device(s): ohci_hcd:usb2
parport0 [7]	i7	derive			Interrupt 7, for device(s): parport0
rtc0 [8]	i8	derive			Interrupt 8, for device(s): rtc0
eth1 [9]	i9	derive			Interrupt 9, for device(s): eth1
Local timer interrupts	iLOC	derive			Local (pr. CPU core) APIC timer interrupt. Until 2.6.21 normaly 250 or 1000 pr second. On modern 'tickless' kernels it more or less reflects how busy the machine is.
Non-maskable interrupts	iNMI	derive			Nonmaskable interrupt. Either 0 or quite high. If it's normaly 0 then just one NMI will often mark some hardware failure.
Performance monitoring interrupts	iPMI	derive			Interrupt PMI (Performance monitoring interrupts)
Performance pending work	iPND	derive			Interrupt PND (Performance pending work)
Spurious interrupts	iSPU	derive			Interrupt SPU (Spurious interrupts)