From: "Terje Bergström" <tbergstrom-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Mark Zhang <nvmarkzhang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: ftrace doesn't work - 1211 upstream kernel
Date: Wed, 12 Dec 2012 14:26:22 +0200 [thread overview]
Message-ID: <50C877EE.60507@nvidia.com> (raw)
In-Reply-To: <50C86A0D.9060009-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 12.12.2012 13:27, Mark Zhang wrote:
> Hi all,
>
> Has anyone tried to use ftrace to debug upstream kernel? I tried today
> but the result is, the serial console hung after ftrace enabled(kernel
> is alive because the Magic SysRq works).
>
> My steps are:
> - Enable CONFIG_FUNCTION_TRACER in kernel config
> - Enter command: echo 0 > /sys/kernel/debug/tracing/tracing_on;echo
> function > /sys/kernel/debug/tracing/current_tracer;echo 1 >
> /proc/sys/kernel/ftrace_dump_on_oops
> - Then sometimes the serial console hangs right after you entered the
> command above, or hangs when you try to "cat /sys/kernel/debug/trace"
>
> I dumped some backtraces(check below, by invoking a system crash
> manually) and hope it helps:
I'm using ftrace to debug host1x driver + tegradrm, running on Tegra2
ventana. I just rebased them on linux-next, and I use just the events,
not function tracing.
echo 1 >/sys/kernel/debug/tracing/events/host1x/enable
~/drm/tests/tegra/2d/tegra_2d_tests
cat /sys/kernel/debug/tracing/trace
I get host1x events as expected.
Also function tracing works.
Terje
next prev parent reply other threads:[~2012-12-12 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 11:27 ftrace doesn't work - 1211 upstream kernel Mark Zhang
[not found] ` <50C86A0D.9060009-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-12 12:26 ` Terje Bergström [this message]
[not found] ` <50C877EE.60507-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-13 2:15 ` Mark Zhang
2012-12-17 22:36 ` Antti P Miettinen
[not found] ` <87bodspaqu.fsf-sS3DoGclAPwgdTl23f3CEMVPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2012-12-18 11:31 ` Mark Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50C877EE.60507@nvidia.com \
--to=tbergstrom-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nvmarkzhang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).