Hi,
On Feb 19, 2013, at 17:58, Adrian Chadd <adr...@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 mptable"
instead of relying on ACPI. I will try that.
As for dtrace, a complete buildworld/installworld cycle didn't change things, I
still get:
# dtrace -n 'syscall:::entry { @num[execname] = count(); }'
dtrace: invalid probe specifier syscall:::entry { @num[execname] = count(); }:
"/usr/lib/dtrace/psinfo.d", line 90: failed to resolve type kernel`struct
thread * for identifier curthread: Module is no longer loaded
Thanks for all the help!
Lars
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
