Date: Sun, 18 Jul 2010 22:06:06 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-current@freebsd.org, Rui Paulo <rpaulo@freebsd.org> Subject: Re: Why is intr taking up so much cpu? Message-ID: <4C43DD3E.2000306@FreeBSD.org> In-Reply-To: <20100718194109.GU2381@deviant.kiev.zoral.com.ua> References: <alpine.BSF.2.00.1007170013191.7378@qbhto.arg> <A81B337F-5932-44B1-BDB4-D9DD36332A16@lavabit.com> <alpine.BSF.2.00.1007171103060.1546@qbhto.arg> <F653FF83-D9CF-42A2-AE9A-B8F914090065@FreeBSD.org> <alpine.BSF.2.00.1007171208010.1538@qbhto.arg> <20100717192128.GM2381@deviant.kiev.zoral.com.ua> <alpine.BSF.2.00.1007180113370.1707@qbhto.arg> <20100718103003.GO2381@deviant.kiev.zoral.com.ua> <4C43541C.3060101@FreeBSD.org> <20100718194109.GU2381@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On 07/18/10 12:41, Kostik Belousov wrote:
> On Sun, Jul 18, 2010 at 12:21:00PM -0700, Doug Barton wrote:
>> On 07/18/10 03:30, Kostik Belousov wrote:
>>> On Sun, Jul 18, 2010 at 01:14:41AM -0700, Doug Barton wrote:
>>>> On Sat, 17 Jul 2010, Kostik Belousov wrote:
>>>>
>>>>> Run top in the mode where all system threads are shown separately
>>>>> (e.g. top -HS seems to do it), then watch what thread eats the processor.
>>>>
>>>> And the winner is!
>>>>
>>>> 11 root -32 - 0K 168K WAIT 0 0:28 18.02% {swi4:
>>>> clock}
>>>> 11 root 21 -64 - 0K 168K WAIT 0 1:17 18.90% intr
>>>>
>>>> The first is with -H, the second without.
>>>
>>> Most likely it is some callout handling. Just in case, do you have
>>> console screensaver active ?
>>
>> I assume you mean "saver=yes" in rc.conf, and the answer is no, I am not
>> using that. Usually I run xscreensaver, but at the time this happened I
>> was not. I do have DPMS enabled in my X config though.
>>
>> Any suggestions on how to dig deeper on this? Are there any settings I
>> can twiddle to try and mitigate it?
> When intr time starts accumulating again, try to do
> "procstat -kk <intr process pid>" and correlate the clock thread tid
> with the backtrace. Might be, it helps to guess what callouts are eating
> the CPU.
Ok, file attached.
--
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
Computers are useless. They can only give you answers.
-- Pablo Picasso
[-- Attachment #2 --]
PID TID COMM TDNAME KSTACK
11 100004 intr swi1: netisr 0 mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100005 intr swi4: clock mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100006 intr swi4: clock mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100007 intr swi3: vm
11 100014 intr swi6: Giant task mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100015 intr swi6: task queue mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100020 intr swi2: cambio mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100021 intr swi5: +
11 100022 intr irq9: acpi0 mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100023 intr irq16:
11 100024 intr irq256: hdac0 mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100026 intr irq17: wpi0 mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100027 intr irq20: hpet0 uhc mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100032 intr irq21: uhci1
11 100037 intr irq22: uhci2 mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100042 intr irq23: uhci3
11 100052 intr irq14: ata0 mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100053 intr irq15: ata1 mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100055 intr irq1: atkbd0 mi_switch+0x200 ithread_loop+0x1da fork_exit+0xb8 fork_trampoline+0x8
11 100056 intr irq12: psm0
11 100057 intr swi0: uart
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C43DD3E.2000306>