From: jpaul@gdrs.com (jpaul@gdrs.com)
Subject: [ltt-dev] lttctl locks up with RT Linux
Date: Tue, 11 May 2010 16:15:15 -0400 [thread overview]
Message-ID: <A47866F933DF804684068A24BF04A9730862A7F0@gdrs-exchange.gdrs.com> (raw)
In-Reply-To: <20100511151120.GA5013@Krystal>
Turning off CONFIG_RCU_CPU_STALL_DETECTOR does not solve the issue with starting up "lttctl -C" ... that call never returns. I'm no longer getting the stack dumps in /var/log/messages and I still have to hard reboot the system as soft reboot doesn't work.
JP
-----Original Message-----
From: Mathieu Desnoyers [mailto:compudj@krystal.dyndns.org]
Sent: Tue 5/11/2010 11:11 AM
To: John P. Paul
Cc: ltt-dev at lists.casi.polymtl.ca; Paul E. McKenney; linux-rt-users at vger.kernel.org
Subject: Re: [ltt-dev] lttctl locks up with RT Linux
* jpaul at gdrs.com (jpaul at gdrs.com) wrote:
> Thanks Mathieu. I'm going to have to look at this a bit more. This may
> have fixed one problem and cause another as "lttctl -C -w /tmp/trace
> trace1" does not return and I'm getting a stack dump in the messages
> file (see below). The last msg I see from that "lttctl -C" command is
> "lttctl: Creating trace". The "lttctl: Forking lttd" is not displayed.
If you disable RCU stalls detection, does it work ?
[Context for Paul: it's on a -RT kernel, with the LTTng patchset]
Thanks,
Mathieu
--
This is an e-mail from General Dynamics Robotic Systems. It is for the intended recipient only and may contain confidential and privileged information. No one else may read, print, store, copy, forward or act in reliance on it or its attachments. If you are not the intended recipient, please return this message to the sender and delete the message and any attachments from your computer. Your cooperation is appreciated.
next prev parent reply other threads:[~2010-05-11 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A47866F933DF804684068A24BF04A9730862A74C@gdrs-exchange.gdrs.com>
[not found] ` <20100422160601.GB28863@Krystal>
[not found] ` <A47866F933DF804684068A24BF04A97309116C93@gdrs-exchange.gdrs.com>
2010-05-11 11:59 ` Mathieu Desnoyers
2010-05-11 14:50 ` jpaul
2010-05-11 15:11 ` Mathieu Desnoyers
2010-05-11 20:15 ` jpaul [this message]
2010-05-13 18:23 ` Mathieu Desnoyers
2010-05-14 14:33 ` jpaul
2010-05-14 14:56 ` Mathieu Desnoyers
2010-05-11 22:11 ` Paul E. McKenney
2010-05-12 12:26 ` jpaul
2010-05-12 23:10 ` Paul E. McKenney
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=A47866F933DF804684068A24BF04A9730862A7F0@gdrs-exchange.gdrs.com \
--to=jpaul@gdrs.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