Why is intr taking up so much cpu?

Max Laier max at love2party.net
Tue Jul 20 02:50:15 UTC 2010

On Tuesday 20 July 2010 04:33:01 Doug Barton wrote:
> On Mon, 19 Jul 2010, Chris Ruiz wrote:
> > On Mon, Jul 19, 2010 at 8:03 PM, Doug Barton <dougb at freebsd.org> wrote:
> >> I added options KDTRACE_HOOKS to my kernel config, built a new kernel,
> >> and rebooted. I decided to try your script before things went sideways
> >> so I'd have an idea of what to expect, and it didn't work:
> >> 
> >> dtrace: failed to initialize dtrace: DTrace device not available on
> >> system
> >> 
> >> Is there something else I need to do to enable it?
> > 
> > You need to build the kernel with CTF.  Try adding "makeoptions
> > WITH_CTF=yes" to your config and rebuilding your kernel.  There's a
> > blurb in src/UPDATING about other ways to accomplish the same thing.
> Thanks for the suggestion, but no improvement. Doing:
> strings /boot/kernel/kernel | grep -i dtrace
> Shows lots of dtrace-related entries, unlike previous kernels built
> without the KDTRACE_HOOKS option, but same error with Dan's script.

Just a stab in the dark, did you "kldload dtraceall"?  KDTRACE_HOOKS just adds 
the needed linkage for the dtrace modules to work.


More information about the freebsd-current mailing list