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@xxxxxxxxxxxxxxxxxx] Sent: Tue 5/11/2010 11:11 AM To: John P. Paul Cc: ltt-dev@xxxxxxxxxxxxxxxxxxxxx; Paul E. McKenney; linux-rt-users@xxxxxxxxxxxxxxx Subject: Re: [ltt-dev] lttctl locks up with RT Linux * jpaul@xxxxxxxx (jpaul@xxxxxxxx) 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. -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
