Skip site navigation (1)Skip section navigation (2) 
Date:      Wed, 20 Feb 2013 09:38:58 +0000
From:      "Eggert, Lars" <lars@netapp.com>
To:        Adrian Chadd <adrian@freebsd.org>
Cc:        Lars Engels <lars.engels@0x20.net>, "current@freebsd.org" <current@freebsd.org>
Subject:   Re: system 20% busy at all times?
Message-ID:  <D4D47BCFFE5A004F95D707546AC0D7E91F73B158@SACEXCMBX01-PRD.hq.netapp.com>
In-Reply-To: <CAJ-Vmo=PzUA802KrDOtpWBzkqPKqCCP-GrAyS36r19%2BVttv3Fw@mail.gmail.com>
References:  <D4D47BCFFE5A004F95D707546AC0D7E91F72FC53@SACEXCMBX01-PRD.hq.netapp.com> <E0C13149-50DF-4C88-A1AC-8BACA2965687@my.gd> <D4D47BCFFE5A004F95D707546AC0D7E91F72FEA5@SACEXCMBX01-PRD.hq.netapp.com> <36DD2FB4-E26A-4F03-95D9-FFD855957269@my.gd> <D4D47BCFFE5A004F95D707546AC0D7E91F7306B4@SACEXCMBX01-PRD.hq.netapp.com> <8F861CF6-D0FA-4BD2-B73D-24CB247584A1@my.gd> <D4D47BCFFE5A004F95D707546AC0D7E91F730A85@SACEXCMBX01-PRD.hq.netapp.com> <51235EA7.6000208@FreeBSD.org> <D4D47BCFFE5A004F95D707546AC0D7E91F731FFD@SACEXCMBX01-PRD.hq.netapp.com> <20130219121544.GU83110@e-new.0x20.net> <D4D47BCFFE5A004F95D707546AC0D7E91F732587@SACEXCMBX01-PRD.hq.netapp.com> <D4D47BCFFE5A004F95D707546AC0D7E91F732F01@SACEXCMBX01-PRD.hq.netapp.com> <CAJ-Vmo=PzUA802KrDOtpWBzkqPKqCCP-GrAyS36r19%2BVttv3Fw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help 
Hi,

On Feb 19, 2013, at 17:58, Adrian Chadd <adrian@freebsd.org> wrote:
> Try top -HS .. to try and break down the kernel threads.

ACPI is eating the cycles, according to top:

    0 root         8    0     0K   496K -       2   1:13 27.88% kernel{acpi=
_task_2}
    0 root         8    0     0K   496K -       0   1:13 25.68% kernel{acpi=
_task_1}
    0 root         8    0     0K   496K CPU1    1   1:07 23.68% kernel{acpi=
_task_0}

I got an off-list hint that the machine in question requires "device mptabl=
e" instead of relying on ACPI. I will try that.

As for dtrace, a complete buildworld/installworld cycle didn't change thing=
s, I still get:

# dtrace -n 'syscall:::entry { @num[execname] =3D count(); }'
dtrace: invalid probe specifier syscall:::entry { @num[execname] =3D count(=
); }: "/usr/lib/dtrace/psinfo.d", line 90: failed to resolve type kernel`st=
ruct thread * for identifier curthread: Module is no longer loaded

Thanks for all the help!

Lars=

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D4D47BCFFE5A004F95D707546AC0D7E91F73B158>