From owner-freebsd-current@FreeBSD.ORG  Tue Jul 20 02:50:15 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id DD78F1065670;
	Tue, 20 Jul 2010 02:50:15 +0000 (UTC)
	(envelope-from max@love2party.net)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10])
	by mx1.freebsd.org (Postfix) with ESMTP id 703828FC17;
	Tue, 20 Jul 2010 02:50:15 +0000 (UTC)
Received: from f8x64.laiers.local (dslb-088-064-190-223.pools.arcor-ip.net
	[88.64.190.223])
	by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis)
	id 0Lxbep-1P8Z9p1ynr-016az2; Tue, 20 Jul 2010 04:50:14 +0200
From: Max Laier <max@love2party.net>
Organization: FreeBSD
To: freebsd-current@freebsd.org
Date: Tue, 20 Jul 2010 04:50:13 +0200
User-Agent: KMail/1.13.5 (FreeBSD/8.1-RC2; KDE/4.4.5; amd64; ; )
References: <A81B337F-5932-44B1-BDB4-D9DD36332A16@lavabit.com>
	<AANLkTimwRV5jSP6z4_Z51RapkVgfTSHVQrVHONWKjA9B@mail.gmail.com>
	<alpine.BSF.2.00.1007191931040.1694@qbhto.arg>
In-Reply-To: <alpine.BSF.2.00.1007191931040.1694@qbhto.arg>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201007200450.13885.max@love2party.net>
X-Provags-ID: V02:K0:QryeLv3pe5pfMG8HPoIIzONMp8jUextDe1MpBS2NiJG
	/vjii8UyKy9pXOHfVzX+/2QaO4kh4QeyLhPTFQq3dO8Mj3DKLH
	8InptC0uwL5W8FgsoP99tkj7jSDi05cBIqYds+r/HPryCKLJZd
	EmAAIrgisDxB1aXXb8hperB5J01YNgzIDQul0KbKM++dTVJQ6b
	tUVSoUSHCpV/niHUuP3Xg==
Cc: Chris Ruiz <yr.retarded@gmail.com>, Doug Barton <dougb@freebsd.org>
Subject: Re: Why is intr taking up so much cpu?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 02:50:15 -0000

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