From: peppe.cavallaro@st.com (Giuseppe CAVALLARO)
Subject: [ltt-dev] Panic on SH with the Kernel 2.6.30.9
Date: Thu, 07 Jan 2010 16:11:51 +0100 [thread overview]
Message-ID: <4B45F9B7.4010405@st.com> (raw)
Message-ID: <20100107151151.CQOxZRouuiwPmS-tLHRx-iANPUZFndKHWcmXRHsM4_k@z> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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+bcACgkQ2Xo3j31MSSIAAgCghLuvB1Ffbbqp4fCWc0IF9KtR
BL0An3tOxwkKjCCPDA7j4wzNSb7nlmS3
=s1sE
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ltt.log
Type: text/x-log
Size: 18967 bytes
Desc: not available
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100107/6405a2ae/attachment-0003.bin>
next reply other threads:[~2010-01-07 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 15:11 Giuseppe CAVALLARO [this message]
2010-01-07 15:11 ` Giuseppe CAVALLARO
2010-01-07 15:11 ` Giuseppe CAVALLARO
2010-01-07 15:23 ` Mathieu Desnoyers
2010-01-07 15:34 ` Giuseppe CAVALLARO
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=4B45F9B7.4010405@st.com \
--to=peppe.cavallaro@st.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