From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] Kernel Oops during lttctl_start()
Date: Mon, 18 Apr 2011 22:12:34 -0400 [thread overview]
Message-ID: <BLU0-SMTP69CCE56D402EFC0AABE95496900@phx.gbl> (raw)
In-Reply-To: <BLU0-SMTP28D889CD22CFA9DD44101B96900@phx.gbl>
* Mathieu Desnoyers (compudj at krystal.dyndns.org) wrote:
> * Bernd Hufmann (Bernd.Hufmann at ericsson.com) wrote:
[...]
> > Steps to reproduce:
> > - Enable all markers (use ltt-armall)
> > - Start tcf-client
> > - connect <remote>
> > - tcf ltt_control setupTrace "kernel" "0" "h2"
> > - tcf ltt_control setChannelEnable "kernel" "0" "h2" false
> > - tcf ltt_control allocTrace "kernel" "0" "h2"
> > - lttctl_client ltt_control writeTraceLocal "kernel" "0" "h2"
> > "/tmp/h2" 2 false false false
> > - tcf ltt_control startTrace "kernel" "0" "h2"
> >
> > Now, the command startTrace won't return. It hangs on line "if
> > (write(fd, op, strlen(op)) == -1)" of method "lttctl_sendop()" which was
> > called by method "lttctl_start()" (see file liblttctrl.c). Please see
> > attached file "dmesg_start.log" for the dmesg output.
> >
> [...]
> > [ 416.740678] LTT : Tracing not active for trace h5
> > [ 416.740908] LTT state dump begin
> > [ 416.740931] LTT state dump thread start
> > [ 416.743693] LTT state dump end
> > [ 447.956279] LTT: 36 events written in channel metadata (cpu 0, index 0)
> > [ 447.956424] LTT: 54278 events written in channel fs (cpu 0, index 0)
> > [ 447.956468] LTT: 40989 events written in channel fs (cpu 0, index 1)
> > [ 618.382904] LTT : Tracing not active for trace h6
> > [ 618.383350] BUG: unable to handle kernel NULL pointer dereference at 00000014
> > [ 618.383983] IP: [<e080828f>] ltt_trace_start+0x7f/0x190 [ltt_tracer]
>
> This looks like a bug in lttng-modules (the LTTng kernel modules).
> Probably a bug with the way the current LTTng-stable versions handle the
> trace session "templates". The good news is that we are getting rid of
> all that code in the upcoming LTTng (with UST/ltt-sessiond/CTF
> integration), so this bug is very likely to vanish then.
>
> I'll try to have a look.
>
> Thanks for reporting this.
It should be fixed in the lttng-modules.git tree v0.19-stable branch now
(commit e5b34c668a7d7b8aeab9fa2bdbb31eed4eff7929). Can you try again
using this version of lttng-modules and confirm that it fixes your crash
before I post a new lttng-modules v0.19-stable release ?
Thanks,
Mathieu
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2011-04-19 2:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 14:04 Bernd Hufmann
2011-04-18 14:04 ` Bernd Hufmann
2011-04-18 14:04 ` Bernd Hufmann
2011-04-19 1:51 ` Mathieu Desnoyers
2011-04-19 2:12 ` Mathieu Desnoyers [this message]
[not found] ` <BLU0-SMTP1016B6233D3D12D56B4925E96900@phx.gbl>
2011-04-21 11:47 ` Bernd Hufmann
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=BLU0-SMTP69CCE56D402EFC0AABE95496900@phx.gbl \
--to=compudj@krystal.dyndns.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