Dear Max Thanks for the suggestion.
Here are the two outputs of vmstat -i exactly 1 minute apart. Can you give me some advice on this please?
Thanks again for your assistance, Paul #vmstat -i interrupt total rate irq1: atkbd0 5 0 irq4: sio0 131475 2 irq14: ata0 47 0 irq17: em0 34511122 578 irq18: em1 em2 50301687 842 irq23: uhci0 uhci+ 1 0 irq26: arcmsr0 3542212 59 cpu0: timer 119056370 1994 cpu1: timer 119045265 1993 cpu2: timer 119174164 1996 cpu3: timer 119172877 1996 Total 564935225 9462 # vmstat -i interrupt total rate irq1: atkbd0 5 0 irq4: sio0 131610 2 irq14: ata0 47 0 irq17: em0 34540241 577 irq18: em1 em2 50323254 842 irq23: uhci0 uhci+ 1 0 irq26: arcmsr0 3546230 59 cpu0: timer 119176497 1994 cpu1: timer 119165391 1993 cpu2: timer 119294325 1996 cpu3: timer 119293038 1996 Total 565470639 9461 At 07:54 PM 22/04/2007, Max Laier wrote:
"vmstat -i" could help to rule out interrupt storms. "top -S" will show in-kernel threads as will "systat". Maybe these help.
_______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-smp To unsubscribe, send any mail to "[EMAIL PROTECTED]"
