From: somshekar@celestialsys.com (Somshekar ChandrashekarKadam)
Subject: [ltt-dev] ltt-sched unload fails
Date: Fri, 9 Jan 2009 13:57:21 +0530 [thread overview]
Message-ID: <872716d1f985423eb43f9ef57ffe9da3@dr116.cyberspaceindia.com> (raw)
Message-ID: <20090109082721.euiG7VWYODYHqNzfbePI5akVnBYSfs8rOBfmjimaXSQ@z> (raw)
Hi,
Using
0.10.0-pre43 with 2.6.24 kernel. Lttng works fine when made as as built in.
when selected as module with the follwing kernel options. rmmod of ltt-sched fails. below is given O/P
Is module support not stable?. Please share some pointers on this.
Thanks in advance
--------------------------
CONFIG_MARKERS=y
#
# Linux Trace Toolkit
#
CONFIG_LTT_TIMESTAMP=y
CONFIG_HAVE_LTT_UNSTABLE_TSC=y
CONFIG_HAVE_LTT_CLOCK=y
# CONFIG_HAVE_LTT_SYNTHETIC_TSC is not set
CONFIG_HAVE_LTT_DUMP_TABLES=y
CONFIG_LTT=y
CONFIG_LTT_RELAY=m
CONFIG_LTT_SERIALIZE=m
CONFIG_LTT_MARKER_CONTROL=m
CONFIG_LTT_TRACER=m
CONFIG_LTT_ALIGNMENT=y
CONFIG_LTT_VMCORE=y
CONFIG_LTT_HEARTBEAT=y
CONFIG_LTT_NETLINK_CONTROL=m
CONFIG_LTT_STATEDUMP=m
-------------------------------------
O/P
---------------------------------------------------------------------------------
WARNING: at kernel/marker.c:805 marker_probe_unregister_private_data()
Pid: 1232, comm: rmmod Not tainted 2.6.24_atom #4
[<c014d1f2>] marker_probe_unregister_private_data+0x96/0xc8
[<f8873297>] ltt_probe_unregister+0x2b/0x8d [ltt_marker_control]
[<f887d06d>] probe_exit+0xd/0x41 [ltt_sched]
[<c01301b6>] blocking_notifier_call_chain+0x17/0x1a
[<c013aaf0>] sys_delete_module+0x18f/0x1db
[<c0140064>] do_kimage_alloc+0x41/0x14c
[<c01074b9>] do_syscall_trace+0x19b/0x1de
[<c0103df2>] syscall_call+0x7/0xb
[<c0410000>] cache_open+0xf/0x7b
=======================
BUG: unable to handle kernel NULL pointer dereference at virtual address 00000028
printing eip: c014d1f2 *pde = 00000000
Oops: 0002 [#1] PREEMPT
LTT NESTING LEVEL : 0 <0>
Modules linked in: ltt_statedump ltt_serialize ltt_control ltt_marker_control ltt_tracer ltt_sched ltt_relay
Pid: 1232, comm: rmmod Not tainted (2.6.24_atom #4)
EIP: 0060:[<c014d1f2>] EFLAGS: 00010282 CPU: 0
EIP is at marker_probe_unregister_private_data+0x96/0xc8
EAX: c04ea111 EBX: 00000000 ECX: f7490f30 EDX: c04ea111
ESI: f7f3442c EDI: 00000000 EBP: f887d000 ESP: f74abf10
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process rmmod (pid: 1232, ti=f74aa000 task=f7fe4170 task.ti=f74aa000)
Stack: c0490bbd c049cb3a 00000325 c0427e60 f7f3442c f887d780 f7f34368 00000000
f8873297 f887d800 00000000 00000880 f74aa000 f887d06d f74aa000 c01301b6
ffffffff 00000000 c013aaf0 5f74746c 65686373 c0140064 bf976db0 00000081
Call Trace:
[<f8873297>] ltt_probe_unregister+0x2b/0x8d [ltt_marker_control]
[<f887d06d>] probe_exit+0xd/0x41 [ltt_sched]
[<c01301b6>] blocking_notifier_call_chain+0x17/0x1a
[<c013aaf0>] sys_delete_module+0x18f/0x1db
[<c0140064>] do_kimage_alloc+0x41/0x14c
[<c01074b9>] do_syscall_trace+0x19b/0x1de
[<c0103df2>] syscall_call+0x7/0xb
[<c0410000>] cache_open+0xf/0x7b
=======================
Code: 75 29 c7 44 24 0c 60 7e 42 c0 c7 44 24 08 25 03 00 00 c7 44 24 04 3a cb 49 c0 c7 04 24 bd 0b 49 c0 e8 08 03 fd ff e8 43 93 fb ff <89> 7b 28 80 4b 2c 01 ba b6 d2 14 c0 31 ff 8d 43 20 e8 d1 d7 fd
EIP: [<c014d1f2>] marker_probe_unregister_private_data+0x96/0xc8 SS:ESP 0068:f74abf10
---[ end trace f803850988743740 ]---
Regards
Neelu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090109/de848c8e/attachment-0003.htm>
next reply other threads:[~2009-01-09 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 8:27 Somshekar ChandrashekarKadam [this message]
2009-01-09 8:27 ` Somshekar ChandrashekarKadam
2009-01-09 8:27 ` Somshekar ChandrashekarKadam
2009-01-09 14:50 ` Mathieu Desnoyers
2009-01-09 14:56 Somshekar ChandrashekarKadam
2009-01-09 14:56 ` Somshekar ChandrashekarKadam
2009-01-09 14:56 ` Somshekar ChandrashekarKadam
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=872716d1f985423eb43f9ef57ffe9da3@dr116.cyberspaceindia.com \
--to=somshekar@celestialsys.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