From mboxrd@z Thu Jan 1 00:00:00 1970 From: peppe.cavallaro@st.com (Giuseppe CAVALLARO) Date: Thu, 07 Jan 2010 16:34:00 +0100 Subject: [ltt-dev] Panic on SH with the Kernel 2.6.30.9 In-Reply-To: <20100107152353.GA16027@Krystal> References: <4B45F9B7.4010405@st.com> <20100107152353.GA16027@Krystal> Message-ID: <4B45FEE8.1010004@st.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Mathieu, Mathieu Desnoyers wrote: > You should probably try lttng 0.170 for kernel 2.6.31.6 instead. This > version fixed a lot of bugs discovered by heavy stress-testing. > > I think your problem comes from the new network synchronization markers > added around there versions. They had incorrect type sizes for the event > payload and therefore caused problems. They were fixed a few versions > later. Just disabling the network "extra" instrumentation should also > work. Thanks for this info. Unfortunately, at this moment, I cannot test lttng on a Kernel newer than the 2.6.30.9 but I'll let you know if I have any progresses. Thanks Peppe > Thanks, > > Mathieu > > * Giuseppe CAVALLARO (peppe.cavallaro at st.com) wrote: > Hi Mathieu, > using lttng-0.162 with an STLinux kernel 2.6.30.9, I get a panic (see > the log attached). > I work on an STM board with an SH4-300 CPU (128MiB RAM). > I mount a rooFS via NFS and run the following commands before having the > panic. > > $ ltt-armall > $ lttctl -C -w /tmp/trace1 trace1 |-> ltt-control-0.75 > $ ls -lR / |-> After a few seconds I get > |-> the panic. > > This is my Kernel configuration for LTT: > CONFIG_LTT=y > CONFIG_LTT_FILTER=y > CONFIG_HAVE_LTT_DUMP_TABLES=y > CONFIG_LTT_RELAY_ALLOC=y > CONFIG_LTT_RELAY_LOCKLESS=y > # CONFIG_LTT_RELAY_IRQOFF is not set > # CONFIG_LTT_RELAY_LOCKED is not set > CONFIG_LTT_SERIALIZE=y > CONFIG_LTT_FAST_SERIALIZE=y > CONFIG_LTT_TRACEPROBES=y > CONFIG_LTT_TRACE_CONTROL=y > CONFIG_LTT_TRACER=y > CONFIG_LTT_ALIGNMENT=y > CONFIG_LTT_CHECK_ARCH_EFFICIENT_UNALIGNED_ACCESS=y > CONFIG_LTT_DEBUG_EVENT_SIZE=y > CONFIG_LTT_USERSPACE_EVENT=y > CONFIG_LTT_VMCORE=y > CONFIG_LTT_STATEDUMP=y > CONFIG_LTT_ASCII=y > > Problem happens when I turn-on LTT_TRACEPROBES at config time. > > Welcome advice. > > Regards, > Peppe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktF/ugACgkQ2Xo3j31MSSKS3QCgjGXAQ3kDlVViSDq9H8Afo7MJ PxEAn0VE2tyz6YnKPYOhnGB2MUquBvKL =zeeb -----END PGP SIGNATURE-----