Date: Tue, 20 Jul 2010 04:50:13 +0200 From: Max Laier <max@love2party.net> To: freebsd-current@freebsd.org Cc: Chris Ruiz <yr.retarded@gmail.com>, Doug Barton <dougb@freebsd.org> Subject: Re: Why is intr taking up so much cpu? Message-ID: <201007200450.13885.max@love2party.net> In-Reply-To: <alpine.BSF.2.00.1007191931040.1694@qbhto.arg> References: <A81B337F-5932-44B1-BDB4-D9DD36332A16@lavabit.com> <AANLkTimwRV5jSP6z4_Z51RapkVgfTSHVQrVHONWKjA9B@mail.gmail.com> <alpine.BSF.2.00.1007191931040.1694@qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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. Max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201007200450.13885.max>