Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Apr 2013 14:36:52 +0200
From:      Alexander Leidinger <Alexander@Leidinger.net>
To:        "J.R. Oldroyd" <fbsd@opal.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: DTrace of radeonkms on 9.1
Message-ID:  <20130401143652.00001870@unknown>
In-Reply-To: <20130327180714.5beae7d6@shibato>
References:  <20130327180714.5beae7d6@shibato>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 27 Mar 2013 18:07:14 -0400
"J.R. Oldroyd" <fbsd@opal.com> wrote:

> Is there any known magic involved in getting DTrace to do its thing on
> 9.1-release?
> 
> I am trying to use it to debug a memory leak problem with the
> radeonkms driver under 9.x.

Can you check if you have the same dtrace-problem with -current? I
would expect that 9.1 already has some dtrace-fixes regarding new
probes in run-time loaded modules, this is just to verify this
assumption.

Assuming there is some kind of dead-lock in this module-load interaction
with dtrace, you could modify the radeonkms module to do it's
initialization magic once a sysctl is set to 1, instead of doing this
magic at module-load time. This way you could load the module, start
the dtrace script and then issue the magic sysctl.

Bye,
Alexander.

-- 
http://www.Leidinger.net    Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org       netchild @ FreeBSD.org  : PGP ID = 72077137



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130401143652.00001870>