Interrupt storm detected on "irq17:"; throttling interrupt source
-
Hi.
I have this log interrupt storm detected on "irq17:"; throttling interrupt source (dmesg)
But this a time, no have proble crashes or reboot….
Why this message?
thanks.
-
What is using irq17? What rate is it running?
Check the boot log it may be recorded there or run:
vmstat -i
Steve
-
Hi
vmstat -i
interrupt total rate
irq32: bge0 bge2 576341732 2837
irq36: bge1 bge3 68845131 338
irq1: atkbd0 18 0
irq16: uhci0 671054389 3304
irq17: atapci0 70958016 349
irq20: ehci1 512748 2
irq21: ehci0 304681 1
cpu0:timer 228814106 1126
irq264: ciss0 346144 1
cpu1:timer 80027181 394
cpu6:timer 7360241 36
cpu4:timer 8269382 40
cpu3:timer 17402136 85
cpu5:timer 81737972 402
cpu2:timer 7746460 38
cpu7:timer 33571359 165
Total 1853291696 9124My server have 4 interfaces but only use 3
LAN, DMz with vlan and WAN
MBUF Usage: top 10%
CPU: top 20% (snort) 8core
RAM: top 5% of 32GB
DISCO: 180GB of 5% use.
The log run: Apr 28 19:00:00 check_reload_status Reloading filter for 60 minutes.
And after: Apr 28 19:00:01 kernel interrupt storm detected on "irq17:"; throttling interrupt source
Example:
Apr 28 18:00:01 kernel interrupt storm detected on "irq17:"; throttling interrupt source
Apr 28 18:00:00 check_reload_status Reloading filterApr 28 17:00:02 kernel interrupt storm detected on "irq17:"; throttling interrupt source
Apr 28 17:00:00 check_reload_status Reloading filterApr 28 16:00:01 kernel interrupt storm detected on "irq17:"; throttling interrupt source
Apr 28 16:00:00 check_reload_status Reloading filterfor time 60 minutes. every.
NOTE: Every hour, PfblockerNG update.
-
Try changing the pfBlocker update interval to make sure it is that.
What hardware are you running on?
Steve