Date: Sat, 9 Oct 2010 18:45:07 +0000 From: "b. f." <bf1783@googlemail.com> To: kes-kes@yandex.ru Cc: freebsd-questions@FreeBSD.org Subject: Re: How to obtain which interrupts cause system to hang? Message-ID: <AANLkTi=tFakKntTDqDwboSM%2BNhUCcq=zGy3v5og98Z0x@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
> How to obtain what nasty happen, which process take 36-50% of CPU > resource? It partly depends upon the version of the OS that you are running, your hardware, and your configuration. 2008 interrupts/sec is high, but not improbably so, for kern.hz>=1000, and not beyond the capabilities of today's average computer, although it may not be optimal for your workloads. So it may not actually be a problem with too many interrupts, but rather with some erroneous system accounting. This can happen, for example, if your computer is using some of the deeper power-saving C-states, but using them poorly, as for example in: http://lists.freebsd.org/pipermail/freebsd-current/2010-August/019383.html So you may want to examine, and perhaps adjust, your choice of kernel timers, kern.hz, and power-saving settings. Device polling can also be a factor, if you are using it. b.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=tFakKntTDqDwboSM%2BNhUCcq=zGy3v5og98Z0x>