[ltt-dev] lttctl locks up with RT Linux

[jpaul at gdrs.com]

Greetings:

I'm using a a 2.6.33.2 kernel. I have LTT up and running on the plain vanilla kernel, but "lttctl -D trace1" never returns on the RT version of the same kernel. I've downloaded and integrated the following pieces:

patch-2.6.33.2-lttng-0.211
ltt-control-0.84-07042010
lttv-0.12.31.04072010

Note that I've had to manually apply several of the patches from the patch file. I can provide a list if desired.

After the lockup, I can do an ls on the /tmp/trace directory and see that the following files have a non-zero length (remaining files in the trace directory have a zero length):

fs_0, fs_1, kernel_0, kernel_1

I'm running on an Intel Core2 Duo system. I've built all the LTT components into the kernel, so I do not have to load any modules at runtime. I do execute an ltt-armall prior to issuing any "lttctl -C -w /tmp/trace trace1" commands.

When the above occurs, I usually have to hard power down the machine as a root issued "reboot" does not reboot the machine (even after trying to kill the running ltt processes).

Any suggestions on how to get this working under the RT kernel would be appreciated. Does LTT even function properly for RT kernels? If not, it would be of great benefit to have it do so.  Please let me know if additional debug info would be helpful. 

A couple additional notes:

- LTTV docs state that it requires glib 2.4 or greater. I believe this is incorrect due to the following dependency:

$ rpm -qa glib2
glib2-2.12.3-4.el5_3.1  << my default glib (RHEL5.x base)

state.c: In function ‘copy_process_state’:
state.c:1344: error: ‘GHashTableIter’ undeclared (first use in this function)

I've installed glib-2.22.5 to get around the above issue.

- I've upgraded to gcc-4.3.4 with the glib upgrade (along with some other dependencies).

Thanks Much

JP

--
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.