From: Bernd.Hufmann@ericsson.com (Bernd Hufmann)
Subject: [ltt-dev] Kernel Oops during lttctl_start()
Date: Mon, 18 Apr 2011 10:04:54 -0400 [thread overview]
Message-ID: <4DAC4506.5050705@ericsson.com> (raw)
Message-ID: <20110418140454.IBCT0LaPIn_ioqr_rSKtSZ6p8yURLTcsiR7USXbek2I@z> (raw)
Hello
I was using the LTTng agent to control LTTng Kernel tracing. Everything
worked fine until I tried to disable certain channels (command
setChannelEnable()). Interestingly, this command doesn't fail, however
the sub-subsequent command startTrace() fails. I did some debugging of
the LTTng agent to investigate the problem. I'm able to pin-point the
last line of execution, which is in the library liblttctrl. There is a
crash and the tcf-agent becomes a zombie process (defunc). When I
display kernel messages with the shell command dmesg I see a kernel
oops. After the error occurred, the remote machine has to be rebooted.
I'm not able to debug further and need some support.
Could someone please look into the problem? Please let me know if you
have any questions.
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.
My target node (running in virtualbox) has the following versions installed:
- Ubuntu 10.10
- Instrumented kernel 2.6.35-24 installed from the PPA repository at
https://launchpad.net/~lttng/+archive/ppa
- manually upgraded UST 0.12
- manually upgraded lttng-agent from the git repository
(git.dorsal.polymtl.ca/git/lttng-agent.git), master branch of 23 March 2011
Thank you very much in advance!
Best Regards
Bernd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg_start.log
Type: text/x-log
Size: 31472 bytes
Desc: not available
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20110418/8cacd41f/attachment-0002.bin>
next reply other threads:[~2011-04-18 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 14:04 Bernd Hufmann [this message]
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
[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=4DAC4506.5050705@ericsson.com \
--to=bernd.hufmann@ericsson.com \
/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