Date: Tue, 19 Feb 2013 10:54:31 +0100 From: Fleuriot Damien <ml@my.gd> To: "Eggert, Lars" <lars@netapp.com> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: system 20% busy at all times? Message-ID: <36DD2FB4-E26A-4F03-95D9-FFD855957269@my.gd> In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F72FEA5@SACEXCMBX01-PRD.hq.netapp.com> References: <D4D47BCFFE5A004F95D707546AC0D7E91F72FC53@SACEXCMBX01-PRD.hq.netapp.com> <E0C13149-50DF-4C88-A1AC-8BACA2965687@my.gd> <D4D47BCFFE5A004F95D707546AC0D7E91F72FEA5@SACEXCMBX01-PRD.hq.netapp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 19, 2013, at 10:44 AM, "Eggert, Lars" <lars@netapp.com> wrote:
> Hi,
>=20
> On Feb 19, 2013, at 10:40, Fleuriot Damien <ml@my.gd>
> wrote:
>> What about reviewing top(1) ?
>=20
> top shows the ~20% I mentioned:
>=20
> last pid: 3176; load averages: 0.79, 0.80, 0.84 =
up =
0+14:49:49 09:43:51
> 17 processes: 1 running, 16 sleeping
> CPU: 0.0% user, 0.0% nice, 18.7% system, 0.0% interrupt, 81.3% idle
> Mem: 32M Active, 9456K Inact, 196M Wired, 19M Buf, 15G Free
> Swap:=20
>=20
Ok the ~20% is from the system itself.
>=20
>> or possibly ps(1) aufx
>=20
> # ps -aufx
> USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
> root 10 346.8 0.0 0 64 - RL 6:54PM 2862:46.43 [idle]
> root 0 64.1 0.0 0 496 - DLs 6:54PM 694:47.32 [kernel]
>=20
65% of a CPU core only for the kernel...
>=20
>=20
>> At least you should be able to see what takes up CPU:
>> - system
>> - user processes
>> - interrupts
>=20
> # vmstat -i
> interrupt total rate
> irq3: uart1 11535 0
> irq4: uart0 1227 0
> irq9: acpi0 1989762564 37379
> irq16: uhci0 uhci1+ 393 0
> cpu0:timer 32147924 603
> irq270: em4 1907258 35
> cpu3:timer 63027976 1184
> cpu2:timer 56428246 1060
> cpu1:timer 44799884 841
> Total 2188087007 41104
>=20
> So it seems that irq 9 is firing a whole lot. Why?
And indeed we find your answer here, acpi0 firing up a lot of =
interrupts.
Don't you get any message about that in dmesg -a or /var/log/messages ?
I'd expect something like "interrupt storm blabla=85 source throttled =
blabla.."
=46rom man 4 acpi , in /boot/loader.conf :
hint.acpi.0.disabled=3D1
Set this to 1 to disable all of ACPI. If ACPI has been =
disabled
on your system due to a blacklist entry for your BIOS, you =
can
set this to 0 to re-enable ACPI for testing.
Any chance you could reboot the host with ACPI disabled ?
If that helps your CPU load, try setting this in /boot/loader.conf :
hw.acpi.verbose=3D1
Turn on verbose debugging information about what ACPI is doing.
Hoping this gets some logs :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36DD2FB4-E26A-4F03-95D9-FFD855957269>