From: ali.akyurek.ext@siemens.com (Akyurek, Ali (EXT))
Subject: [ltt-dev] LTTng with 2.6.22.18 and lost events
Date: Thu, 22 Jan 2009 18:19:24 +0100 [thread overview]
Message-ID: <1E65288790442545B413D69F2A8D27DE0463798E@ERLD164A.ww004.siemens.net> (raw)
In-Reply-To: <1E65288790442545B413D69F2A8D27DE0463792E@ERLD164A.ww004.siemens.net>
Hi all,
I've solved the problem with the gui.
Problem is that i'm running the deamon seperate than lttctl, then i
couldn't see facilites message.
After adding -d parameter, i got the facility messages, then i'm able to
see the results with lttv.
But i'm still thinking how to solve lost events problem.
________________________________
Von: Akyurek, Ali (EXT)
Gesendet: Donnerstag, 22. Januar 2009 16:40
An: ltt-dev at lists.casi.polymtl.ca
Betreff: [ltt-dev] LTTng with 2.6.22.18 and lost events
Hi all,
I'm trying LTTng with a 2.6.22.18 kernel on an Arm machine. I've applied
patch-2.6.22-rc4-mm2-lttng-0.9.10 patched with some corrections.
Everything went well, until destroying the channels.
I get the following message:
"LTT : cpu : 6769 events lost in cpu channel (cpu 0)."
So when i try to open with lttv-gui, it doesn't work.
I've searched but found nothing except Mathieu, saying that it may be
related to buffer size or timestamp.
Is there anyone having an idea?
Thanks.
Mit freundlichem Gruss / Best Regards
Ali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090122/b6c3530b/attachment-0002.htm>
WARNING: multiple messages have this Message-ID
From: ali.akyurek.ext@siemens.com (Akyurek, Ali (EXT))
Subject: [ltt-dev] LTTng with 2.6.22.18 and lost events
Date: Thu, 22 Jan 2009 18:19:24 +0100 [thread overview]
Message-ID: <1E65288790442545B413D69F2A8D27DE0463798E@ERLD164A.ww004.siemens.net> (raw)
Message-ID: <20090122171924.LNBwzDizSUSnCMMAwoceYRVH8wziLjHsj5hBIpxWQJU@z> (raw)
In-Reply-To: <1E65288790442545B413D69F2A8D27DE0463792E@ERLD164A.ww004.siemens.net>
Hi all,
I've solved the problem with the gui.
Problem is that i'm running the deamon seperate than lttctl, then i
couldn't see facilites message.
After adding -d parameter, i got the facility messages, then i'm able to
see the results with lttv.
But i'm still thinking how to solve lost events problem.
________________________________
Von: Akyurek, Ali (EXT)
Gesendet: Donnerstag, 22. Januar 2009 16:40
An: ltt-dev at lists.casi.polymtl.ca
Betreff: [ltt-dev] LTTng with 2.6.22.18 and lost events
Hi all,
I'm trying LTTng with a 2.6.22.18 kernel on an Arm machine. I've applied
patch-2.6.22-rc4-mm2-lttng-0.9.10 patched with some corrections.
Everything went well, until destroying the channels.
I get the following message:
"LTT : cpu : 6769 events lost in cpu channel (cpu 0)."
So when i try to open with lttv-gui, it doesn't work.
I've searched but found nothing except Mathieu, saying that it may be
related to buffer size or timestamp.
Is there anyone having an idea?
Thanks.
Mit freundlichem Gruss / Best Regards
Ali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090122/b6c3530b/attachment-0003.htm>
WARNING: multiple messages have this Message-ID
From: ali.akyurek.ext@siemens.com (Akyurek, Ali (EXT))
Subject: [ltt-dev] LTTng with 2.6.22.18 and lost events
Date: Thu, 22 Jan 2009 18:19:24 +0100 [thread overview]
Message-ID: <1E65288790442545B413D69F2A8D27DE0463798E@ERLD164A.ww004.siemens.net> (raw)
Message-ID: <20090122171924.Owm9AfyDy-UGBrPg4jN2ltE_xp2TDoaprjV-nd1ySO0@z> (raw)
In-Reply-To: <1E65288790442545B413D69F2A8D27DE0463792E@ERLD164A.ww004.siemens.net>
Hi all,
I've solved the problem with the gui.
Problem is that i'm running the deamon seperate than lttctl, then i
couldn't see facilites message.
After adding -d parameter, i got the facility messages, then i'm able to
see the results with lttv.
But i'm still thinking how to solve lost events problem.
________________________________
Von: Akyurek, Ali (EXT)
Gesendet: Donnerstag, 22. Januar 2009 16:40
An: ltt-dev at lists.casi.polymtl.ca
Betreff: [ltt-dev] LTTng with 2.6.22.18 and lost events
Hi all,
I'm trying LTTng with a 2.6.22.18 kernel on an Arm machine. I've applied
patch-2.6.22-rc4-mm2-lttng-0.9.10 patched with some corrections.
Everything went well, until destroying the channels.
I get the following message:
"LTT : cpu : 6769 events lost in cpu channel (cpu 0)."
So when i try to open with lttv-gui, it doesn't work.
I've searched but found nothing except Mathieu, saying that it may be
related to buffer size or timestamp.
Is there anyone having an idea?
Thanks.
Mit freundlichem Gruss / Best Regards
Ali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20090122/b6c3530b/attachment.htm>
next prev parent reply other threads:[~2009-01-22 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 15:39 Akyurek, Ali (EXT)
2009-01-22 15:39 ` Akyurek, Ali (EXT)
2009-01-22 15:39 ` Akyurek, Ali (EXT)
2009-01-22 17:19 ` Akyurek, Ali (EXT) [this message]
2009-01-22 17:19 ` Akyurek, Ali (EXT)
2009-01-22 17:19 ` Akyurek, Ali (EXT)
2009-01-22 20:06 ` Mathieu Desnoyers
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=1E65288790442545B413D69F2A8D27DE0463798E@ERLD164A.ww004.siemens.net \
--to=ali.akyurek.ext@siemens.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