daily graph
weekly graph
monthly graph
yearly graph
five-year graph

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 i0 derive Interrupt 0, for device(s): timer
i8042 i1 derive Interrupt 1, for device(s): i8042
cascade i2 derive Interrupt 2, for device(s): cascade
serial i4 derive Interrupt 4, for device(s): serial
ohci_hcd:usb2 i5 derive Interrupt 5, for device(s): ohci_hcd:usb2
7 i7 derive
rtc0 i8 derive Interrupt 8, for device(s): rtc0
ehci_hcd:usb1, eth0, eth1 i9 derive Interrupt 9, for device(s): ehci_hcd:usb1, eth0, eth1
pata_rdc i14 derive Interrupt 14, for device(s): pata_rdc
pata_rdc i15 derive Interrupt 15, for device(s): pata_rdc
Non-maskable interrupts iNMI derive Interrupt NMI, for device(s): Non-maskable interrupts
Local timer interrupts iLOC derive Interrupt LOC, for device(s): Local timer interrupts
Spurious interrupts iSPU derive Interrupt SPU, for device(s): Spurious interrupts
Performance monitoring interrupts iPMI derive Interrupt PMI, for device(s): Performance monitoring interrupts
IRQ work interrupts iIWI derive Interrupt IWI, for device(s): IRQ work interrupts
APIC ICR read retries iRTR derive Interrupt RTR, for device(s): APIC ICR read retries
Hypervisor callback interrupts iHYP derive Interrupt HYP, for device(s): Hypervisor callback interrupts
ERR iERR derive
MIS iMIS derive
This page was generated by munin version 2.0.49 (modified by czo) at 2025-04-30 10:27:12+0200 (CEST).